|
||||||||
|
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/groups/opt_out.
Sergey, I may not have made myself clear.
For example:
Project 'A' is the project you wish to run in parallel.
Project 'A' has a bunch of really long shell/bat commands and requires some sort of post-build action that is causing this defect.
Which is: if Project 'A' is run in parallel and contains post-build actions, it will not release until it completes.
The solution: Create a second project 'B' that contains all your post-build actions from 'A'.
Finally, remove all the post-build actions in 'A' (as they are all duplicated in project 'B') and have 'A' trigger 'B' as the final step.
Additional notes:
You will need to use the "NodeLabel Parameter Plugin" to ensure that this project is run on the same machine.
You may also need to give it the ${WORKSPACE} parameter (and any others) if your post-build actions need to manipulate the artefacts generated from Project 'A'.