|
||||||||
|
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/d/optout.
I am clueless on Jenkins development so I cant recommend which method to use. However the following is my use case
1. Able to run mvn -B release:prepare release:perform on both master and slave. Very likely on slave. I build snapshot at Jenkins slave and use jenkins maven release plugin to run cut the release using the same workspace
2. release:prepare at master and then fan out/in to all slaves to the rest ( ie viewable using jenkins build pipeline plugin). This is our java+native mulitplatform build
for both cases, I am using manual view workspace
So it is important for me have current workspace with a known hostname for fast client workspace discovery
Perhaps we can do some experiment to add this as an option?
Thank you for looking into this