Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Deprecated: This plugin has been removed from the Jenkins Update Centre

Please use the ArtifactDeployer Plugin for publishing/deploying artifacts from a workspace to remote locations.
Archived versions of this plugin remain available for download.

Plugin Information

No information for the plugin 'copyarchiver' is available. It may have been removed from distribution.

The objective is to aggregate archived artifacts from several jobs into a shared directory.
For each job, only archived artifacts of the last success build will be copied.

Project Configuration

The archived artifacts will be copied in the specified shared directory. For each job, the base directory is the archived directory. And you can use wildcards like 'module/dist/*/.zip'.
For the shared directory, you can use build timestamp variable ${BUILD_ID}. By default, this variable uses the pattern 'YYYY-MM-DD_hh-mm-ss'. You can change this format by providing your own pattern.


* Fixing JENKINS-5837
* Fixing JENKINS-5482


Release 0.5.1 (July 08, 2010)

* Integrated JENKINS-6862 fix

Release 0.5 (June 20, 2010)

* Deleted the ability to customize the BUILD_ID format. The feature is given by the lastest version of the zentimestamp Hudson plugin.

Release 0.4.3 (March 15, 2010)

* Fixed JENKINS-5765

Release 0.4.2 (October 11, 2009)

* Fixed the regression introduced with copyarchiver 0.4 : the base directory for scanning artifacts is the workspace and not the module root

Release 0.4.1 (October 11, 2009)

* Added backward compatibility with copyarchiver 0.3
* Affected the value of the deleteSharedDirectory option to true

Release 0.4 (October 05, 2009)

* Fixed bug : the copyarchiver doesn't work on the first build
* Added the ability to delete the shared directory and its content

Release 0.3 (July 06, 2009)

* Fixed the flatten issue for remote run
* Added the ability to search into all the workspace (not only the SCM module root) if the selected job for archiving is the current job
* Added the replacement of environment variables and build variables for the 'includes' field and the 'excludes' field.

Release 0.2 (July 01, 2009)

* Added the flatten feature
Ignore the directory structure of the source files and copy all files into the directory specified in 'Shared directory' section.

* Allowed to copy archived artifacts for the current job
If the selected job to copy is the current project, use the workspace base directory.

* Add the ability to use build variables in the 'shared directory' section.

Release 0.1 (June 28, 2009)

* Initial release


  1. Unknown User (sbouchet)


    It seems the copy-archiver plugin needs a 1.6 JVM to run. is this right ? i cannot find any informations about that.

  2. Unknown User (gboissinot)

    This issue has been resolved with CopyArchiver 0.4

  3. Unknown User (tomer g)

    Is it possible to copy the build result to more than one shared directory?

  4. Unknown User (gregoryboissinot)

    This feature is currently not available. It has been reported in the issue JENKINS-5482.

    In progress...

    1. Unknown User (tomer g)

      When do you think it will be available?

      I wonder if I should write ANT task or wait for the new version (smile)

  5. Unknown User (kjelle)


    Will there be any extention to this plugin which allows to reach the Shared Directory through Hudson? (e.g. the same link as to artifacts for last successful build)

    1. Unknown User (gregoryboissinot)

      There is no this feature in the current version of plugin. However, it's a good idea. Could you fill in a enhancement issue

  6. Unknown User (ddamours)

    it seems that the plugin always copies artifacts to the master server.

    Is there an option to make a copy to the current slave server?

    1. Unknown User (gbois)

      For your usage, I suggest you should switch to the ArtifactDeployer plug-in.
      This plug-in meets your needs.