Ok, it's running the integration tests again... we are back in business
On 29 August 2017 at 21:51, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> https://builds.apache.org/blue/organizations/jenkins/
> maven-3.x-jenkinsfile/detail/master/128/pipeline more corectly
>
> On 29 August
https://builds.apache.org/blue/organizations/jenkins/maven-3.x-jenkinsfile/detail/master/128/pipeline
more corectly
On 29 August 2017 at 21:49, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Let's see how https://builds.apache.org/blue/organizations/jenkins/
> maven-3.x-jenkinsfile/
Let's see how
https://builds.apache.org/blue/organizations/jenkins/maven-3.x-jenkinsfile/branches/
goes now...
On 29 August 2017 at 19:40, Karl Heinz Marbaise wrote:
> Hi,
>
> On 29/08/17 20:35, Stephen Connolly wrote:
>
>> Should support but not require same names integration branch...
>>
>
> Y
Hi,
On 29/08/17 20:35, Stephen Connolly wrote:
Should support but not require same names integration branch...
Yes that was my assumption as well...
>likely
the Jenkinsfile needs updating after JENKINS-43507
Ah ok...
Thanks for clearing up things...
Kind regards
Karl Heinz Marbaise
O
Should support but not require same names integration branch... likely the
Jenkinsfile needs updating after JENKINS-43507
On Tue 29 Aug 2017 at 19:17, Karl Heinz Marbaise wrote:
> Hi,
>
> currently I'm observing that I can a branch in Maven Core for example
> MNG-6216 but it looks like I need a
Hi,
currently I'm observing that I can a branch in Maven Core for example
MNG-6216 but it looks like I need also the same branch in the
maven-integration-testing...
Currently the configuration lets conclude me that:
Checking for first existing branch from [MNG-6216, master]...
> git rev-par
