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
 Setup Jenkins build which uploads file to File Release System

To upload build results to a file release in CollabNet SourceForge Enterprise or CollabNet Teamforge, configure the file release component as a post-build action in Jenkins.

Before you set up the CollabNet plugin, make sure that the CollabNet SorceForge or Teamforge project contains valid package and file release folders. 

  1. In the Hudson interface for the job, click Configure.
  2. In the Post-build Actions section, select CollabNet File Release.
  3. Enter the URL of the CollabNet site. For example, https://forge.collab.net.
  4. Enter the username and password of the CollabNet project member who will upload the files.
  5. Enter the name of the CollabNet project, the package and the file release where you want the build files added.
  6. Specify whether you want existing files with the same name to be overwritten.
  7. Specify a file pattern so that files that match the pattern are uploaded. You may use Hudson environmental variables in your file patterns. For example, pkg/subversion-r $ {SVN_REVISION).tar.gz,  in a job to build Subversion source code.
  8. Click Save.

 The File Release plugin can be used to upload any workspace artifact to the File Release system.  It can be configured as a post-build action or a promoted-builds action. The file release user must have permission to upload add file releases in the project.  Below is how a promoted-builds setup might look.

The resulting files will be in the File Release System, like so:

  • No labels


  1. Unknown User (ideallorn)

    It seems that the "Alpha" must be a pre-created/existing release, why you can not use variable defined name, something like "%Build_Number%".

  2. Unknown User (ampa)

    +1 5 years later to Dan. Are there any plans to have environment variables accessible from File Release Upload? Continuous Delivery is so close yet so far without it...

  3. Unknown User (otafasd)

    +1 Dan Zhang's request