[JIRA] (JENKINS-44172) Better scan of multibranch pipelines

[mdealer@gmail.com (JIRA)]

Edgars Batna commented on JENKINS-44172

Re: Better scan of multibranch pipelines Following features need to be clearly separated: Load Jobs into Jenkins from SCM Execute these Jobs The scanning of a multibranch pipeline should not be triggering anything at all. Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[mdealer@gmail.com (JIRA)]

Edgars Batna edited a comment on JENKINS-44172

Re: Better scan of multibranch pipelines

Following features need to be clearly separated:

# Load Jobs into Jenkins from SCM # Execute these Jobs The scanning of a multibranch pipeline should not be triggering anything at all and I bet there are other problems that require workarounds because of this .

Add Comment

[tim.webster@gmail.com (JIRA)]

Tim Webster commented on JENKINS-44172

Re: Better scan of multibranch pipelines

Another to disable automatic building after the scan is if you have all your jobs in jobdsl and frequently rebuild it.  We use Jenkins which is 100% configured with code running in a container.  If there is a major configuration change (i.e. changing plugins), the container needs to be re-created.  For this reason we also don't persist the workspace. If you re-create the container and it does a scan, you get a gazillion jobs running all of a sudden. For this reason we ditched multibranch.  However I'm on another project now that uses Github Organizations, which uses multibranch implicitly so having to face this again now. Also from what I've read if you can disable automatic SCM triggering as a workaroud, but this will  also disable builds from webhooks (correct me if I'm wrong)

Add Comment

[tim.webster@gmail.com (JIRA)]

Tim Webster edited a comment on JENKINS-44172

Re: Better scan of multibranch pipelines

Another reason to disable automatic building after the scan is if you have all your jobs in jobdsl and frequently rebuild it.  We use Jenkins which is 100% configured with code running in a container.  If there is a major configuration change (i.e. changing plugins), the container needs to be re-created.  For this reason we also don't persist the workspace.

If you re-create the container and it does a scan, you get a gazillion jobs running all of a sudden. For this reason we ditched multibranch.  However I'm on another project now that uses Github Organizations, which uses multibranch implicitly so having to face this again now. Also from what I've read if you can disable automatic SCM triggering as a workaroud, but this will  also disable builds from webhooks (correct me if I'm wrong)

Add Comment

[mark@kakapo.co.nz (JIRA)]

Mark Wright commented on JENKINS-44172

Re: Better scan of multibranch pipelines

Just to reiterate the comments of Edgars Batna and Tim Webster, we have a large number of jobs configured with the job DSL. Restarting Jenkins for any reason is a nightmare, as the branch scanning triggers a multitude of jobs. We generally have to spend some time killing the jobs in order to free resources for the builds we actually want. Like Tim, I'm under the impression that the only workaround is to disable the automatic SCM triggering which would also disable triggering from webhooks (which we don't want to do).

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[Sovietaced@gmail.com (JIRA)]

Jason Parraga commented on JENKINS-44172

Re: Better scan of multibranch pipelines

After moving to multi branch pipelines our company has experienced issues with the branch scanning. We have a few integration test style jobs which run for about 2 hours and each job may have between 20-40 open pull requests (arguably, this is an issue itself). Anyway, every time the branches are scanned our build queue blows up and we cannot check in code for roughly a day unless we spend time killing many of those jobs. Since we have a few jobs like this, this happens a couple times a week. We would really benefit from being able to specify a cron expression for scanning. This would allow us to at least scan during off peak hours like on the weekends so there is minimal disruption. Right now we are at the mercy of the configured interval which I assume begins when you make the interval configuration.

Add Comment

[jenkins@xca.ch (JIRA)]

Lorenz Aebi commented on JENKINS-44172

Re: Better scan of multibranch pipelines

Is there any progress on this? Or are there other solutions to solve the problem with polling the SCM?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)