|
||||||||
|
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.
Hi,
Ok, I think we are both confused here. I will start with my confusions and then address yours.
I am using Jenkins version 1.554.3. I am using Maven Project Plugin 2.5.
When I create a maven project in Jenkins, the job has three sections. Pre steps, Main Build and Post Steps. If I add a maven invoking pre step and purposely make it fail, then the entire job stops at the pre step. However, if I add a "execute system groovy script" (which I believe is part of the groovy plugin) as a pre build step, and purposely cause that script to throw an exception, the build does not stop and causes subsequent post build steps to run.
My initial thoughts were that this should be posted against the groovy plugin, however as I am writing this I can see that perhaps this should be posted against the maven project plugin. Are you saying the post build and pre build steps that are part of a maven project in Jenkins is part of Jenkins core functionality? If so I will update the component to this.
Thank you and apologies for the requirement to clarify this.