|
||||||||
|
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.
Ok after further investigation I noticed that builds after the Jenkins/Plugin upgrade no longer the show “Parsing Ivy Descriptor Files” in the console output. But builds before do.
I believe the only happens if you have an "Ivy Project" and DO NOT have the "Build modules as separate jobs" clicked under the advanced option. This issues appears to have been introduced in this commit “Only parse ivy descriptor files when required.”:
https://github.com/jenkinsci/ivy-plugin/commit/dbc83c6230115347fda4bba0372d7bc79942913c#diff-25d902c24283ab8cfbac54dfa101ad31
The method parseIvyDescriptorFiles(listener, logger, envVars) at line 375 appears to have been moved under the if (!project.isAggregatorStyleBuild()) condition. Meaning anyone without that option set never gets dependencies parsed. I have patched this locally and it appears to work again. I’d contribute a patch but not sure if moving this back to where it is supposed to be would affect the rest of this commit?