|
||||||||||||||
|
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.
The previous storage format was ambiguous about what was a parameter filter and what was part of the job path for e.g. matrix jobs. As of 1.26 an unambiguous format is used.
There is a one-time migration which attempts to guess what you meant in the old case: if there is a / in the name, and there is a = in the name, and no job with the specified full name exists, then the name is split on the last /, with the first part being the project name and the second part being the parameter filter. Otherwise the name is assumed to be a matrix project name and the parameters field is left empty.
I am not surprised that this heuristic is not correct in every case but I am not sure if it can be improved. If you think it can, please file a pull request against this plugin with a test demonstrating the more precise migration using @LocalData.