|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I had one somewhat-unrelated question. You mention that externals should be avoided if possible - do you know of another way of managing complex sets of dependencies between subsystems without using externals? I am working in a C++ shop so we don't have the luxury of advanced dependency management tools like Maven, Nexus and such..... Externals seem like the only practical solution for this in our case.
Also, just so you know, all three of the "potential use cases" I outlined above we actually do use (or have tried) at our site... so they aren't really "potential" in that regard.![]()
And option #1 is our most common usage pattern at the moment.