PM, Sami Tikka wrote:
> >> >>
> >> >> This is just a wild guess because I do not use windows: Could it be
> >> >> Jenkins aborts the build when it sees the "exit 2" ?
> >> >>
> >> >> For Linux and Mac versions of Je
t;> >>
>> >> For Linux and Mac versions of Jenkins it is a sign of failure when a
>> >> build
>> >> script exits with non-zero exit code.
>> >>
>> >> -- Sami
>> >>
>> >> bearrito kirjoitti 9.8.2012 kello
r Linux and Mac versions of Jenkins it is a sign of failure when a
> build
> >> script exits with non-zero exit code.
> >>
> >> -- Sami
> >>
> >> bearrito kirjoitti 9.8.2012 kello
> 20.59:
> >>
> >> Jenkins will randomly not execute ba
>>
>> -- Sami
>>
>> bearrito kirjoitti 9.8.2012 kello 20.59:
>>
>> Jenkins will randomly not execute batch files as part of the build.
>>
>> In the failing case I get a message like :
>>
>> 18:01:43 C:\JenkinsHome\Slave\workspace\Job1>e
on-zero exit code.
>
> -- Sami
>
> bearrito kirjoitti 9.8.2012 kello 20.59:
>
> Jenkins will randomly not execute batch files as part of the build.
>
> In the failing case I get a message like :
>
> *18:01:43* C:\JenkinsHome\Slave\workspace\Job1>exit 2 *18:01:44* Build
ello 20.59:
> Jenkins will randomly not execute batch files as part of the build.
>
> In the failing case I get a message like :
>
> 18:01:43 C:\JenkinsHome\Slave\workspace\Job1>exit 2
> 18:01:44 Build step 'Execute Windows batch command' marked build as failure
>
>
Jenkins will randomly not execute batch files as part of the build.
In the failing case I get a message like :
*18:01:43* C:\JenkinsHome\Slave\workspace\Job1>exit 2 *18:01:44* Build step
'Execute Windows batch command' marked build as failure
In the successful case I get
