|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Is build status case sensitive in your check? I have two post-build failures that I tried.
One is with xUnit{/color:red}
Building in workspace /var/lib/jenkins/workspace/Test![]()
, 1 deletion![]()
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:wiseloren/finance.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:wiseloren/finance.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:wiseloren/finance.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 7553bf2bc81d6086400b9274e52e806e5fc90374 (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7553bf2bc81d6086400b9274e52e806e5fc90374
> git rev-list 7553bf2bc81d6086400b9274e52e806e5fc90374 # timeout=10
[Test] $ /bin/sh -xe /tmp/hudson4989245979488022036.sh
+ date
+ git add date.txt
+ git commit -m test
[detached HEAD f3d92b4] test
1 file changed, 1 insertion
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing PHPUnit-3.x (default)
[xUnit] [INFO] - [PHPUnit-3.x (default)] - 1 test report file(s) were found with the pattern 'build/logs/junit.xml' relative to '/var/lib/jenkins/workspace/Test' for the testing framework 'PHPUnit-3.x (default)'.
[xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run?
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
Build step 'Publish xUnit test result report' changed build result to FAILURE
Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.
Finished: FAILURE
Crap4J{/color:red}
Building in workspace /var/lib/jenkins/workspace/Test![]()
, 1 deletion![]()
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:wiseloren/finance.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:wiseloren/finance.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:wiseloren/finance.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision 7553bf2bc81d6086400b9274e52e806e5fc90374 (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7553bf2bc81d6086400b9274e52e806e5fc90374
> git rev-list 7553bf2bc81d6086400b9274e52e806e5fc90374 # timeout=10
[Test] $ /bin/sh -xe /tmp/hudson7046176554547474773.sh
+ date
+ git add date.txt
+ git commit -m test
[detached HEAD 4f7619c] test
1 file changed, 1 insertion
[CRAP4J] Collecting Crap4J analysis files...
[CRAP4J] Searching for report files within build/logs/crap4j2.xml
[CRAP4J] Using the new FileSetBuilder
[CRAP4J] No crap4j report files were found. Configuration error?
Build step 'Report Crap' marked build as failure
Pushing HEAD to branch develop at repo origin
Finished: FAILURE
In both cases, Jenkins recognizes a job failure, but only in one case does the push not happen. The main difference I'm noticing is that CRAP4J marks it as failure not FAILURE. Thus, I'm thinking Jenkins must be case insensitive where the other plugins are case sensitive. (Your plugin isn't the only one missing the marking as a failure there.) If that is the case, I'll submit a bug request to CRAP4J (though it might be good for your check to be case insensitive since jenkins is).