Just a thought - are the successes and failures both running on the
same agent box? If not, then perhaps one is configured differently
than the other.
Scott
On Thu, Aug 9, 2012 at 9:04 PM, j.barrett strausser
<j.barrett.straus...@gmail.com> wrote:
> That's absolutely the reason it is being marked as failure. Jenkins
> interprets non-zero codes as failure. The question is why it exits with 2 to
> begin with.
> The batch file is just wrapping a call to powershell but when it fails it
> appears to never even make the call to poweshell.
>
>
> On Thu, Aug 9, 2012 at 5:49 PM, Sami Tikka <sjti...@gmail.com> 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 Jenkins it is a sign of failure when a build
>> script exits with non-zero exit code.
>>
>> -- Sami
>>
>> bearrito <j.barrett.straus...@gmail.com> 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 step 'Execute Windows batch command' marked build as
>> failure
>>
>>
>> In the successful case I get
>>
>>
>> 11:40:37 C:\JenkinsHome\Slave\workspace\Job1l>exit 0
>> 11:40:37 [SrcInfrastructureYellowSql] $ powershell.exe "&
>> 'C:\Users\#Jenkins\AppData\Local\Temp\hudson5725866031798325048.ps1'"
>> 11:40:53 [SrcInfrastructureYellowSql] $ cmd /c call
>> C:\Users\#Jenkins\AppData\Local\Temp\hudson2668871926239131897.bat
>> 11:40:53
>> 11:40:53 C:\JenkinsHome\Slave\workspace\Job1>powershell.exe "&
>> {C:\JenkinsHome\Slave\workspace\Job1\Job2\script.ps1; exit $lastexitcode}"
>>
>>
>> It seems as though the powershell session is not able to be started?
>>
>> Any hints on this?
>>
>>
>>
>
