Set up a build to generate CollabNet tracker artifacts

Configure the Tracker component as a post-build action to generate new CollabNet SourceForge Enterprise or CollabNet TeamForge tracker artifacts or update existing artifacts based on Hudson build results.

1. In the Hudson interface for the job, click Configure.
2. In the Post-build Actions section, select CollabNet Tracker.
3. Enter the URL of the CollabNet site. For example, https://forge.collab.net.
4. Enter the username and password of the SourceForge or TeamForge project member responsible for creating and updating tracker artifacts in the project.
5. Enter the name of the project containing the tracker.
   Note: If the user specified is not a member of this project, the plugin will not be able to locate the project.
6. Enter the name of the tracker where artifacts will be created or updated.
   Note: If the user specified does not have the requisite permissions in this tracker, the plugin will not be able to identify the tracker.
7. Enter a title for the tracker artifact. You may use environment variables in the title. For example, ${BUILD_ID). Entering a title that could change causes a new artifact to be opened every time the build fails. For a title that does not change, all build results affect a single tracker artifact.
8. Specify the individual to whom the artifact should be assigned.
   Note: If the project administrator has configured the tracker to automatically assign artifacts to individuals based on artifact criteria, skip this step. If not, and you do not select a user, the artifact is assigned to "None". The artifact is also assigned to "None" in case the username is not valid.
9. Enter a priority for the artifact.
10. Select whether you want the Hudson build log attached to the artifact. Attaching the build log could be especially useful when a build fails, since you would not need to check the Hudson console output for details.
11. Specify whether you want the artifact to be updated irrespective of the outcome of the build.
    • Select yes if you always want to update the issue after each build, regardless of whether the build succeeds or fails.
    • Select no if you only want to track build failures.
12. Select whether you want an open artifact to be automatically closed when the build succeeds.
    Note:

    • Use this option only to update existing artifacts. If the artifact is a new one, it will have the status "Open" for a non-successful Hudson build, and "Closed" for a successful build.
    • Make sure your selection does not potentially conflict with a tracker workflow rule you may have set up. For example, assume you had defined a status transition rule that an open artifact can be closed only when the "Fixed in Release" field is specified. If you select the "Yes" option here to automatically close an open artifact without manual intervention, there will be a conflict because of the "Fixed in Release" requirement.
13. If the artifact represents a failed build for a file release, enter the release name in Reported Release.