|
||||||||
|
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.
There is corresponding option in Jenkins new build job creation.
I have tried create new build job based on the old one with new value of the Integrity - CM Configuration Name and new build job name. The saving of the updated config failed with error.
Does it mean that we can't create new build jobs based on the old one?
In this case why not to use name of the build job as value for Integrity - CM Configuration Name? It is unique for sure between all build jobs. In this case Integrity - CM Configuration Name entry in the config editing could be removed or made fixed. Migration to the new plugin will require just re save configs and the jobs builds history will be still available.
Another option is creating unique value of the Integrity - CM Configuration Name each time when build job config is saved, just new UUID or new GUID value, which will be saved in the job config.xml but not available for editing. This will require to re save all build jobs configurations after migration to the new plugin version but the jobs build history will be not affected!