To upload only specific, successful builds, configure the Hudson Promoted Builds plugin to
publish those build files to a SourceForge or TeamForge release.
A "promoted build" in Hudson is a build that succeeds and also meets the criteria that
you specify.
Note: This feature requires the Hudson Promoted Builds plugin as well as the
CollabNet file release component.
Let's say you set up a job, "Subversion_Build", to build
open source Subversion, and you want to promote builds by manually approving them.
-
In the Hudson interface for the job, click Configure.
-
Select Promote builds when...
-
Enter a name for the promotion process and select Only when manually
approved as the criterion for promoting a successful build.
-
In the Actions section for the promotion process, enter the URL of
the CollabNet site. For example, https://forge.collab.net.
-
Enter the username and password of the CollabNet project member who will upload the files.
Note: This user must have at least view permission for the package.
-
Enter the name of the SourceForge or TeamForge project, the package and the file
release where you want the build files added.
Note: A package, and within that, a release, must exist before you can add individual files to
that release.
-
Specify whether you want existing files with the same name to be overwritten.
-
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".
-
Click Save.
When the build succeeds and is promoted, it is uploaded into the CollabNet file release
application.
Note: To upload all builds to a CollabNet file release, whether promoted or not,
you need to configure the File Release System component as a post-build action.