Yes. And the branch job will be deleted automatically after you delete the branch (we can set an orphaned item strategy if we want to keep them around for a while)
On Mon 9 Jan 2017 at 22:44, Christian Schulte <c...@schulte.it> wrote: > Am 01/09/17 um 23:36 schrieb Stephen Connolly: > > > Yes, every branch that has the Jenkinsfile will automatically get its own > > > branch job build within 15 minutes of being pushed. > > > > > > (It would be faster - i.e. 5s after the push - but until I don't want to > > > pester infra to upgrade Jenkins until I have got some stability in the > > > branch-api 2.0.x series) > > > > > > There is also ever cooler when I get > > > https://github.com/jenkinsci/workflow-multibranch-plugin/pull/46 merged > and > > > released... > > > > > > The Jenkinsfile will then use *the matching integration test branch if it > > > exists* and fall back to master if missing... so you will be able to even > > > get the results of the new integration tests before merging... but > that's a > > > few weeks away I suspect > > > > Very cool. So I can prepare a local branch per issue, push that, wait > > for Jenkins to build it and if everything went well, pick the commit > > into master and remove the branch afterwards? > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- Sent from my phone
