This plugin makes it possible to copy artifacts to remote locations.
By default, Jenkins archives artifacts generated by the build. These
artifacts are stored in the JENKINS_HOME directory with all other
elements such as job configuration files.
There is no separation between infrastructure elements, project elements and outputs.
It is often considered to be a bad practice and it doesn't help to manage JENKINS_HOME directory from an administrator point of view (backup issues, etc).
And for now, we can't change the 'Archived artifacts' location.
ArtifactDeployer plugin enables you to archive build artifacts to any remote locations such as to a separate file server (outside of JENKINS_HOME directory).
There are many other Jenkins plugins close to ArtifactDeployer such as
publishing artifacts from Jenkins resources (from the current workspace,
from the old builds of the same job or other jobs, ...) to remote
locations with the protocol file://
There are also others plugins for managing other protocols such as ftp://, ssh:///.
But none of these plugins provides a common way to manage the deployment.
ArtifactDeployer is a complete alternative to the built-in Jenkins feature "Archiving artefacts' and it is aimed at providing an uniform deployment mechanism.
- Copies build artifacts from the workspace to a remote location shared on the build processor node
- Provides links to archived artefacts from the job status page
- Deletes on demand archived artifacts when the build is removed
- Only file deployment is supported
- For downloading deployed artifacts, remote location must be accessible from the Jenkins master
- Jenkins process must have the right permissions to write in the specified location
* Fix SECURITY-294 - Rips out the ability to execute a Groovy script with this plugin
* Fix deployed item ID when there is multiple ArtifactDeployer step
* Fix JENKINS-24140 - ArtifactDeployer migration breaks lazy-load on Jenkins initialization
* Fix typo in help file.
* Additional help text
* Fix JENKINS-18135 - Conditional Build Step plugin crashes when using Artifact Deployer plugin as build step
* Fix NullPointterException
* Fix JENKINS-16031 - Lost deployed artifacts after restart
* Fix JENKINS-15709 - ArtifactDeployer does not appear in Flexible Publish
* Fix JENKINS-15354 - Add option to fail the build if specified "Files to deploy" do not exist
* Fix JENKINS-15059 - recursive deletion of deployment pathes not working correctly
* Fix JENKINS-15058 - Setting for GroovyScript is not permanent
* Fix JENKINS-14547 - Null pointer exception when using groovy script
* Fix JENKINS-14548 - help for groovy script usage is never displayed
* Fix JENKINS-13841 - "Base folder" for deploying the artifacty from source folder to remote directory
* Fix JENKINS-13937 - ArtifactDeployer 0.16 messes the filenames for Windows filesystems
* Fix NullPointerException on artifact deletion
* Fix JENKINS-12311 - Display the Deployed Artifacts in a tree structure similar to how they are displayed under the Build Artifacts section
* Fix JENKINS-11867 - Deployed files have a different time with original files.
* Fix JENKINS-12522 - Deploy artifacts for failed builds, too
* Fix JENKINS-11640 - Can't copy on remote windows slave
* Fix partially JENKINS-9996 - Have the possibility to change the user and group ACL's on artifacts (Conserve file permissions to copy).
* Fixed NullPointerException when the remote directory value is not set (for the ArtifactDeployer publisher and for the ArtifactDeployer builder).
* Make it compatible to LTS series (1.409.x)
* Complete fix JENKINS-10360 - Added support of Matrix project
* Fix partially JENKINS-10360 - Added support of Maven project
* Fix slave execution
* Fix bug on deletion
* The deployed artifacts in the Jenkins dashboard are now sorted.
* Fix a ClassCastException (for more than one entry) on save configuration
* Integrated a pull request - Fixed a NullPointerException
* Add 'deployment artifacts' as a a build step (builder item) in
addition to publishers.
Use Case: In the same job as build steps: Build your artifacts, deploy them in remote locations (as servers) and launch the integration tests.
* Add a checkbox for deleting remote artifacts when the build is deleted.
* The plugins enables users to call a Groovy script when the builds are deleted (for manual and automatic deletion).
* Initial release
Only the filesystem protocol is available