|
||||||||
|
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.
With the Crap4J plugin, I can see that the build is reported as a failure, but the git publisher still pushes the changes.
I don't know if that is expected or not, since both the Git publisher and Crap4J are post build actions. I'll need to ask on the mailing list for the expected behavior of post-build actions when one of the post-build actions fails.
As an example of the potential conflict between the results of post-build actions, if 3 post-build actions are defined on a job, and the first action succeeds, but the second action fails, should the job be considered failed? In my case the job was marked as failed.
If the first action succeeds and the second action fails, should the third action be executed at all? In my case, there were 2 post-build actions. The log seems to indicate that the Crap4J action may have finished before the git publisher action, though I can't be absolutely sure. In my case, I believe the Crap4J action was first and caused the job to be marked as failed, but did not cause the publisher push to be stopped.
Started by user Mark Waite Building remotely on centos7x64 (7.0.1406 CentOS amd64-CentOS-7.0.1406 linux CentOS-7.0.1406 amd64-CentOS amd64) in workspace /var/lib/jenkins/mark-pc1-slave/workspace/JENKINS-24833-git-publishes-always > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url ssh://mwaite@mark-pc1/var/lib/git/mwaite/bugs/JENKINS-24833.git # timeout=10 Fetching upstream changes from ssh://mwaite@mark-pc1/var/lib/git/mwaite/bugs/JENKINS-24833.git > git --version # timeout=10 using GIT_SSH to set credentials mwaite@mark-pc1 > git fetch --tags --progress ssh://mwaite@mark-pc1/var/lib/git/mwaite/bugs/JENKINS-24833.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 Checking out Revision 0ac1e6fd10414a191c58f6fb0a6cb11c90644ea0 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0ac1e6fd10414a191c58f6fb0a6cb11c90644ea0 > git rev-list 0ac1e6fd10414a191c58f6fb0a6cb11c90644ea0 # timeout=10 [JENKINS-24833-git-publishes-always] $ python add_a_file.py rm 'tmpoeSqtg' [detached HEAD b1c7ef1] Removed tmp fles 1 file changed, 1 deletion(-) delete mode 100644 tmpoeSqtg [detached HEAD 529312a] Added /var/lib/jenkins/mark-pc1-slave/workspace/JENKINS-24833-git-publishes-always/tmpyFk42u 1 file changed, 1 insertion(+) create mode 100644 tmpyFk42u [CRAP4J] Collecting Crap4J analysis files... [CRAP4J] Searching for report files within *.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 master at repo origin using GIT_SSH to set credentials mwaite@mark-pc1 > git push ssh://mwaite@mark-pc1/var/lib/git/mwaite/bugs/JENKINS-24833.git HEAD:master Finished: FAILURE