Do not trigger all branch builds when regenerating a multibranchPipelineJob

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      This is a super annoying issue that makes the jobDsl plugin really hard to use in some situations.

       

      When it regenerates a multibranchPipeline job, all the branch builds are triggered. Of course, this can mean that hundreds of builds are suddenly scheduled. This should, in my opinion, either:

       

      a) never happen

      b) or only happen when there are actual configuration changes.

            Assignee:
            Daniel Spilker
            Reporter:
            Costin Caraivan
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: