If you need to run against a different IT branch, then change
https://github.com/apache/maven/blob/master/Jenkinsfile#L22 to point to the
branch on integration tests here are the options:

1. (Ideal option) Create a *throwaway* branch on maven.git specifically for
the integration test run where you change
https://github.com/apache/maven/blob/master/Jenkinsfile#L22 to point to
your maven-integration-testing.git branch name. Get a clean run on that
*throwaway* branch and then merge the integration tests and throw-away the
throw-away branch.

This lets us see that the integration tests remain passing without code
changes.

2. (OK option) using
https://builds.apache.org/job/maven-jenkinsfile/job/MNG-5958/lastCompletedBuild/replay/
if you can login to Jenkins

We need to go look at the Jenkinsfile that you ran and we do not have
tracability of the diff... plus you are running the tests with the new
changed code... may want to consider this in conjunction with #1 if you
have any doubt that the new code will not work with the new tests

3. (Yuk option) push the change to your branch, get the passing build, then
force push your branch back to HEAD^1

On 19 January 2017 at 11:30, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> https://builds.apache.org/job/maven-jenkinsfile/job/MNG-5958/ is failing
>
> Do not commit without showing a passing build
>
> On 19 January 2017 at 11:12, Christian Schulte <c...@schulte.it> wrote:
>
>> Am 16.01.2017 um 02:48 schrieb Christian Schulte:
>> > Commit to review is here:
>> >
>> > <https://git-wip-us.apache.org/repos/asf?p=maven-integration
>> -testing.git;a=commit;h=2fd74ac6d4747b11d50b78965f0d2c229fb46773>
>> >
>> > If no one objects until Thursday, 19th, 2017, I'll merge it to master.
>>
>> If no one objects, I will merge it in a few hours.
>>
>> Regards,
>> --
>> Christian
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>

Reply via email to