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 On Mon 9 Jan 2017 at 22:27, Christian Schulte <c...@schulte.it> wrote: > Am 01/09/17 um 22:44 schrieb Stephen Connolly: > > > Can we stage this logical set of changes on the same branch before > merging > > > to master (so we know we have a clean test run on the > > > https://builds.apache.org/job/maven-jenkinsfile/ branch build) > > > > What's this Jenkinsfile about? Does it mean whenever someone creates a > > branch from master with that Jenkinsfile and pushes it, Jenkins will > > pick up that branch and perform a build of it and run the ITs against > > it? That would be mega cool. Instead of cherry picking the commits > > sequentially into master, there better be some intermediate branch with > > all those commits which can then be merged into master in one go. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- Sent from my phone
