Currently always running against the master branch of integration tests... the Jenkins plugin with resolving matching branches is not released yet
On Tue 10 Jan 2017 at 23:42, Christian Schulte <c...@schulte.it> wrote: > Am 01/09/17 um 23:53 schrieb Stephen Connolly: > > > 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) > > > > Hi, > > > > can you please take a look at the maven-jenkinsfile/MNG-5958 job. Did it > > really run the ITs from the branch with the same name or did it run the > > master branch ITs? There is an IT failing I would not have expected to > > fail. It's the IT in question to be changed in that other thread. So if > > it did run the master branch ITs, the old IT will fail with MNG-5958 > > applied to the core. Maybe it's better to always let the master branch > > ITs run in addition to the ITs from the branch. Does not matter if such > > a build takes half a day, IMHO. > > > > Regards, > > -- > > Christian > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- Sent from my phone
