Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: ivytrigger-plugin
-
Labels:None
-
Similar Issues:
Description
According to https://wiki.jenkins-ci.org/display/JENKINS/IvyTrigger+Plugin
Note: The plugin uses only persistence in memory. There is no impact on the Jenkins infrastructure (no new files created).
However, we've seen in practice that all depended-upon artifacts are downloaded to a ivy-trigger-cache directory outside the workspace. I'd expect that there would have to be some XML files downloaded and persisted between checks, but downloading all the depended-upon artifacts is really putting a strain on build machines handling multiple, very large, builds.
I'm not sure if this is a requirement of the Ivy library, or if is really is possible to do a resolve without an implicit download. If it is however, that would be ideal for both my poor aching disks and for the network.
Code changed in jenkins
User: Robert Clark
Path:
src/main/java/org/jenkinsci/plugins/ivytrigger/IvyTrigger.java
src/main/java/org/jenkinsci/plugins/ivytrigger/IvyTriggerEvaluator.java
src/main/resources/org/jenkinsci/plugins/ivytrigger/IvyTrigger/config.jelly
src/main/resources/org/jenkinsci/plugins/ivytrigger/IvyTrigger/help-downloadArtifacts.html
http://jenkins-ci.org/commit/ivytrigger-plugin/3897869272b82adaeb9b19eecb9194e1c632da15
Log:
Added option to control whether or not artifacts are downloaded
There is a new option (downloadArtifacts) that controls whether or not
artifacts are downloaded. If they are (the default to maintain backwards
compatibility) then the trigger will check to see if any artifacts inside
a dependency have changed with out changing the version number.
If artifacts are not configured for download, the trigger only checks to
make sure the resolved dependency version has not changed.
Fixes
JENKINS-28044