Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38552

Multibranch pipeline (re)creation intelligence

      When a multibranch pipeline is created or recreated, it instantly pulls in all the branches at once and starts initial builds on them.

      Could we have a way to limit the number of builds which happen right at branch creation? Something user configurable would be great.

          [JENKINS-38552] Multibranch pipeline (re)creation intelligence

          Alex Taylor created issue -
          Jesse Glick made changes -
          Component/s New: branch-api-plugin [ 18621 ]
          Component/s Original: workflow-multibranch-plugin [ 21465 ]

          "Skip initial build on first branch indexing" would be awesome.

          Ing. Christoph Obexer added a comment - "Skip initial build on first branch indexing" would be awesome.
          Stephen Connolly made changes -
          Attachment New: Screen Shot 2017-02-24 at 14.57.19.png [ 36136 ]

          Is this just that you want the Throttle builds property available for pipeline multibranch?

          Stephen Connolly added a comment - Is this just that you want the Throttle builds property available for pipeline multibranch?

          Alex Taylor added a comment -

          stephenconnolly I would say yes that could work fine if we had TCB enabled for pipeline. Do we need a separate defect for multibranch and TCB plugin or will the pipeline one suffice?

          Alex Taylor added a comment - stephenconnolly I would say yes that could work fine if we had TCB enabled for pipeline. Do we need a separate defect for multibranch and TCB plugin or will the pipeline one suffice?

          Ok, so this is a bug in either branch-api or workflow-multibranch that the RateLimitBranchProperty is not configurable for pipeline multibranch sources

          Stephen Connolly added a comment - Ok, so this is a bug in either branch-api or workflow-multibranch that the RateLimitBranchProperty is not configurable for pipeline multibranch sources
          Stephen Connolly made changes -
          Labels New: scm-api-tidy-scrub

          Why is the first build in every existing branch/pr useful at all?

          There are workflows that leave lots of open branches and such a build storm isn't useful at all - throttling doesn't help at all IMO.

          Storing the top commit during first import as last built would make a lot more sense IMO.

          Ing. Christoph Obexer added a comment - Why is the first build in every existing branch/pr useful at all? There are workflows that leave lots of open branches and such a build storm isn't useful at all - throttling doesn't help at all IMO. Storing the top commit during first import as last built would make a lot more sense IMO.
          Stephen Connolly made changes -
          Labels Original: scm-api-tidy-scrub New: scm-api-tidy-rfe

            fbelzunc FĂ©lix Belzunce Arcos
            ataylor Alex Taylor
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: