|
||||||||
|
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/d/optout.
Thanks Christian for implementing this. It will really help. Some notes about how we are using Jenkins fwiw:
1 - All of our projects are "free-style software projects." With the Jenkins Gradle plugin installed, this provides an optional Gradle "Build Step" for any project. We add this build step to each project. Within this build step would be a good place to provide a checkbox that says "Automatically build downstream dependencies". This way the support would be optional.
2 - Our projects are multi-module. In the root-level build.gradle we have a version number defined. In the sub projects we apply from ../build.gradle and depend on compile: $coords + 'artifact' + $ver. ($coords and $ver being defined in ../build.gradle). I don't think this should affect the plugin though since you are getting the dependency information directly from Gradle which correctly resolves the variables for the artifact.
3 - All of our dependencies are resolved using the gradle maven plugin from an artifact repository (Nexus).