|
||||||||
|
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.
It seems we found a workaround.
First, it seems to be necessary to specify the paths of the settings.xml files in the job itself, even though they are set in the global settings. Previously affected jobs now run again. (However - the other ones derived from the template are fine with the global settings only.)
As to the above error message:
Some jobs, like the one I took the error log from, have their poms in a subdirectory. It seems that the Maven plugin version we had before (lower than 2.6) was somehow satisfied to be given the path "D:\...\subdirectory" instead of "D:\...\subdirectory\pom.xml". That was how the job had been working for about a year. Adding "\pom.xml" solved the problem.
So - problem solved, issue closed, I guess.