Plugin Information

The CollabNet Plugin is an integration with CollabNet TeamForge. Don't have TeamForge yet?  Try our free 90-day trial.

Provided features include:

• Authenticate users from TeamForge.  If setup as the "Build & Test" application, it can even use Single Sign-On.
• Authorization from TeamForge, including the ability to set permissions in Hudson based on roles in your TeamForge project.
• Upload the build log or workspace artifacts to the TeamForge Documents.
• Upload workspace artifacts to the TeamForge File Release System, as a post-build publishing task or as a build promotion task.
• Open/update/close TeamForge Tracker artifacts based on the Hudson build status.
• Upload workspace artifacts to the Lab Management Project Build Library.  (Requires CollabNet Lab Management).

Requirements:

The CollabNet Plugin requires the  Promoted Builds Plugin.

The CollabNet Plugin requires the  Subversion Plugin .

The CollabNet Plugin requires a CollabNet TeamForge 5.2+ or CollabNet SourceForge 5.0 + server.  The Authorization component will only work with CollabNet TeamForge 5.2 or later.

The Lab Management PBL Upload component requires a CollabNet Lab Management server.  But don't worry, all the other components will work just fine without it.

Configuring Components:

Authentication/Authorization:

For general instructions on how to setup Authentication/Authorization, visit help.collab.net.

Setup for the Authentication and Authorization components starts on the main Hudson configuration page. 



You'll need to check "Enable Security", choose "CollabNet Authentication" and "CollabNet Authorization".  Authorization will not work if you do not also use CollabNet Authentication.  The authorization information obtained from TeamForge are cached for the specified duration or until the end of a user session (logging out of Hudson).  You'll need to manually add any other users/groups you'd like to have admin access.  It's a good idea to add your own username here, so you don't lock yourself out.  The read-only section is currently a no-op.  All users who can properly authenticate will be granted READ permissions throughout Hudson.
The Authorization component also allows you to associate each Hudson job with a TeamForge project.  Hudson-specific roles in the TeamForge project will grant permissions in Hudson.  



 These roles can be automatically created by checking a box, if you are a project admin in the project.  Also, you may choose to grant default roles (project admins have all rights; members have read).

Document Uploader:

For general instructions on how to setup the Document Uploader, visit help.collab.net.

The Document Uploader can be used to upload any artifacts from the Hudson workspace or the Build Log for the job.  The user specified must have permissions to upload documents in the project.



 The resulting documents (if the build was successful) will be in the TeamForge Documents. 

File Release:

For general instructions on how to setup the File Release component, visit help.collab.net.

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:

 Tracker:

For general instructions on how to setup the Tracker component, visit help.collab.net.

The Tracker component can be used to open a new artifact on failure or always update an artifact.  You can choose to automatically close the issue once the build succeeds, or just update the last comment this this effect. 

If you give the issue title a name with a build variable in it, it will open a new issue on any failure (instead of updating).  The user needs to have the right to edit Tracker artifacts.



The resulting tracker artifact will look something like:

ScmViewer for Subversion:

Collabnet TeamForge can now be selected to be used as the Repository browser.

Project Build Library:

For general instructions on how to setup the Project Build Library component, visit help.collab.net.

The Project Build Library component requires  CollabNet Lab Management.  Like File Release, it may be used as a post-build action or as a promoted-builds action.  Below is an example of how to configure it as a post-build action.



The resulting files will appear in the Lab Management Project Build Library, like so:

Help/Support:

Installation help and configuration help are available on help.collab.net.

Please submit any questions to the TeamForge forum.

 FAQ:

   1.  Does this integrate with / update the SFEE Plugin?

        No, the  SFEE Plugin is a separate plugin that is not maintained by CollabNet.  It works with CollabNet SourceForge 4.4, so it may be a good choice if you have an older version.  Our plugin is not a direct upgrade.  If you change from using the SFEE Plugin to the CollabNet Plugin, you will have to reconfigure your jobs appropriately.  You should be able to use both plugins simultaneously, if you wish, although it might be a bit confusing.

   2.  Uploads fail when using an SSL-enabled TeamForge server.  What do I do?

        You'll need to add the server's certificate to your java keystore on the Hudson server.  First dowload the certificate to your Hudson server.  You should be able to get it by opening a browser window on the TeamForge server, viewing the certificate associated with that page, and exporting the certificate file.  Then, you'll need to run something like "sudo keytool -keystore $JAVA_HOME/jre/lib/security/cacerts -import -file teamforge.cert".  (On Windows, replace $JAVA_HOME with %JAVA_HOME%).  If you haven't changed your java keystore's password, it will be "changeit".  After you've imported the cert to the java instance that Hudson is using, it should be able to upload.

   3.  I'm having problems with login and logout when using CollabNet Authentication.  It seems to be redirecting to an unexpected site.

        Go to the Hudson configure page and look in the Email Notifacation section. The CollabNet plugin uses the value of the Hudson URL set here for redirection. If it's wrong, logins will go astray. Check that it's set to the real Hudson URL.

   4.  I've setup authentication, but can no longer get to the "Manage Hudson" pages.&nbps; How do I get back into the system?

        As long as you have access to the machine and user running Hudson, you'll be able to get back in. Just log into the machine. Find the Hudson home (by default, this will be the ~/.hudson directory of the user running Hudson). Edit the config.xml, changing the value for "useSecurity" to false. Restart Hudson and you should not need to log in to get access.

Changelog:

Version 1.1.5:  Released 4/22/2010.

• Feature addition: Added configurable authorization cache when using TeamForge authorization to reduce load generated on TeamForge server
• Feature addition: Passwords are stored more securely

Version 1.1.4:  Released 3/26/2010.

• Bug fix: SVN tagging plugin does not work with 1.1.3

Version 1.1.3:  Released 2/26/2010.

• Bug fix: A ClassCastException that caused builds to fail when the Tracker or Document Uploader component was enabled, is now fixed.
• Feature addition: CollabNet Build & Test reauthenticates when TeamForge Single Sign On tokens from another user are observed.
• Feature addition: A Hudson job that is not associated with a TeamForge project can now be viewed and configured by all authenticated users.

Version 1.1.2:  Released 12/21/2009.

• Bug fix: FRS now can upload when using master/slave configuration
• Bug fix: Error message related to Promoted Build plugin during startup
• Bug fix: Having a trailing "/" in a CollabNet TeamForge URL ended the user's session and prevented single sign-on with Hudson
• Feature addition: You can now use TeamForge's ScmViewer as the subversion repository viewer
• Feature addition: You can enable/disable SSO between Hudson and CollabNet TeamForge

Version 1.1.1:  Released 09/03/2009.

• Bug fix: Fixed a 500 error when the plugin is installed using some browsers (IE 8 and Chrome)
• Bug fix: Fixed problem where triggered builds in Hudson (e.g., periodic build or poll scm) won't run if CollabNet Authorization is in use.
• Bug fix: Fixed problems that caused incorrect redirection on logging
• Bug fix: Fixed problem where, for some users, the 'Assigned to' field in the Tracker component could not be set

Version 1.1:  Released 07/20/2009:

• Fix to make file uploads faster (as of r17463).
• Feature addition: Allow system-wide shared authentication which can be overridden for individual components (as of r18043).
• Bug fix: Fixed errors that occurred when running Hudson in an iFrame in IE (r18646).
• Bug fix: Fixed bug where SSO was not working on very first page load (r18684).

Version 1.0:  Released 04/14/2009.