Conditionally publish gradle artifacts
Currently, when someone reviews the code, Jenkins selects those assemblies, analyzes, etc. and then publishes the Artifactory artifact (currently using the Jenkins Artifactory plugin, but happily moving to pure gradle).
Also, this code is tests (unit and automated acceptance tests), so it seems useless to create and deploy a new artifact for the artifactory, which in turn requires deploying and running automated tests when the commit only affects the test code.
How can I skip the publish step if the application code hasn't changed?
+3
source to share
No one has answered this question yet
Check out similar questions: