|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Regarding post-build deliver, the plugin does not currently support that, just the initial SCM phase.
In the interim, it's possible to add a step to the build to invoke JBE as a one-off to run a particular phase of the build, e.g.:
jbe -repository REPO_ADDR -userId USER_ID -passwordFile PASSWORD_FILE -engineId ENGINE_ID -buildResultUUID $buildResultUUID -participants com.ibm.team.build.autoDeliver -noComplete -verbose
Where $buildResultUUID is the property within Jenkins containing the build result UUID.
Can also use -pass PASSWORD if you're not using a password file, but there's a risk then that the password would appear in the build log.