![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
14/Dec/12 1:10 PM
|
|
Description:
|
I would like to be able to condition the outcome of a build for each build step, in a generic way (independently of the type of build step). What I mean is basically to generalize to any type of build step the three options provided by a parameterized trigger (https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin) build step when it is set to block (i.e. "Fail this build step if the triggered build is worse or equal to", "Mark this build as failure if the triggered build is worse or equal to" and "Mark this build as unstable if the triggered build is worse or equal to").
This would allow a more fine-grained control of the impact of each build step (e.g. "Don't fail/interrupt the build because this build step failed, but do mark the build as failure at the end...").
My use case:
- startup Tomcat with my application
- run some build steps (some ant targets, some shell build steps, etc)
- stop Tomcat
- do some more stuff
The problem is I want to make sure the build step that stops Tomcat always runs if the startup ran, even if the steps in between failed. However, the build should be marked as failure in the end if those failed.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Jose Pedro Correia
|
|
|
|
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
|
