Find plugins

SFEE1.0.4Minimum Jenkins requirement: 1.361ID: sfee

Authenticate users and publish build artifacts relying on a Collabnet Source Forge Enterprise Edition (SFEE) server.

What is this?

This plugin extends Hudson in order to integrate with a SFEE (Collabnet Source Forge Enterprise Edition) server.

This integration allows you to use SFEE database to perform user authentication, and to publish build artifacts to a SFEE project's release folder

Supported SFEE is 4.3 onwards.

This plugin requires description setter plugin to be installed too.

Configuring SFEE server 

In the Configure System section of your Hudson server, insert informations related to the SFEE server. Remember that username inerted will be used to perform artifacts publishing and SFEE queries.

SFEE  host name should be specified  without the http/s prefix (eg, sfee.open.collab.net)

 Configuring user access control and authorizations

If you want, you can configure the plugin in order to validate the username/password against the SFEE database. It is also possible (using a matrix based authorization strategy) to specify which users/roles are allowed to publish build artifacts to SFEE server. (The "CollabNet Authorization" strategy in section "Authorization" will only be available as soon as SFEE server 5.2 is released - so the user permission matrix is left to the Hudson features for matrix based autorization strategy).

In oder to enable these features, Hudson security should be activated. The "enable security" in off when installing Hudson for the first time.

Activating Job Publishing

In order to perform a Job publishing, you have to configure the Job properties and select the associated SFEE Project, Release Package, the rules related to automatic build publishing and release name.

In order to do this, open Hudson Job configuration page.


The release name can be either specified as fixed name (eg MyFirstRelease in the Release Name field) or extracted from the build log via the regular expression specified in the Release Name regexp field.
In this latter case, the Release Name field will be used to specify the selection group of the regular expression.

In the example below, if in the build log appears a line like SFEE Revision: MYPROJECT-0.1, the release name will be MYPROJECT-0.1


Publish a build

When a build ends successfully, it is possible to publish the build logs and the artifacts to the SFEE server (if Upload automatically after build checkbox is not selected).

Just choose the build you want to publish from the Build History Widget and click on SourceForge action link.

As default, all artifacts but the build log will be uploaded. This rule also applies when the automatic upload is activated.

After a build has been succesfully published, accessing a build history item will show SFEE release infos


ArchivesGet past versions