|
||||||||
|
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.
Correct. Unfortunately we haven't found a tool capable of doing this inspection / analysis automatically - at least not for C++ / Visual Studio projects. Thus we have little choice other than manually coding / recoding the dependencies in Jenkins. It is annoying and fragile, I know, but in the absence of any other reasonable alternative we have no other choice.
The problem I have is that, even when I want to do this manual configuration myself I currently need to make use of at least a dozen different plugins to accomplish the task, and since each plugin is developed by different individuals they vary in quality and compatibility. On more than one occasion I've had to take extensive measures to work around compatibility issues between plugins where some don't work quite properly with others.
My hope is that if this basic job-dependency management logic were incorporated into the core Jenkins architecture the results of these efforts would be more fruitful.