The CollabNet Plugin is an integration with CollabNet TeamForge.
Provided features include:
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.
Following individual component can be configured within each Jenkins job
Please submit any questions to the TeamForge forum.
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 Jenkins server. First dowload the certificate to your Jenkins 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 Jenkins 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 Jenkins configure page and look in the Email Notifacation section. The CollabNet plugin uses the value of the Jenkins URL set here for redirection. If it's wrong, logins will go astray. Check that it's set to the real Jenkins URL.
4. I've setup authentication, but can no longer get to the "Manage Jenkins" pages.&nbps; How do I get back into the system?
As long as you have access to the machine and user running Jenkins, you'll be able to get back in. Just log into the machine. Find the Jenkins home (by default, this will be the ~/.jenkins or ~/.hudson directory of the user running Jenkins). Edit the config.xml, changing the value for "useSecurity" to false. Restart Jenkins and you should not need to log in to get access.
Version 2.0.5: Released 05/25/2018.
Version 2.0.4: Released 09/08/2017.
Introduce 'publishEventQ' pipeline step. This step will report the current pipeline job status to TeamForge EventQ server (Pull request #19)
Version 2.0.3: Released 05/27/2017.
Version 2.0.2: Released 11/28/2016.
Version 2.0.1: Released 11/25/2016.
Version 2.0.0: Not released.
Version 1.2.0: Released 5/11/2016.
Version 1.1.10: Released 10/11/2015.
Version 1.1.9: Released 10/10/2013.
Version 1.1.8: Released 5/16/2013.
Version 1.1.7: Released 2/27/2013.
Version 1.1.6: Released 3/12/2011.
Version 1.1.5: Released 4/22/2010.
Version 1.1.4: Released 3/26/2010.
Version 1.1.3: Released 2/26/2010.
Version 1.1.2: Released 12/21/2009.
Version 1.1.1: Released 09/03/2009.
Version 1.1: Released 07/20/2009:
Version 1.0: Released 04/14/2009.