Tuleap 11.12 March 2020

Jenkins Integration

We are currently very busy with integrations and especially with Jenkins to offer the best-in-class experience when using both tools. With Tuleap 11.12 two major blocks are already available:

Tuleap Branch Source Jenkins plugin v2

It’s almost a complete rewrite of the Branch Source plugin that we released ~ one year ago. The main focus was on making the authentication more robust and more performant. The only supported method of authentication is through Access Keys   (until now it was basic auth with login/password). Access Keys are easier to revoke when they get compromised and are generally easier to rotate to ensure a healthy and secure environment.

In addition to authentication, the way build jobs are triggered also changed. With v1 of the plugin, developers had to rely on weird tricks in their Jenkins file or regular polling of the source repositories to get their jobs triggered when a push was done. With v2, a new endpoint (URL) is exposed (similar to what notify Commit does for regular git repo). When this endpoint is called, it will automatically trigger build of jobs that corresponds to the given git repository URL. Sounds complex? Fear not! Tuleap will do that automatically for you, see the next section!

Project wide push trigger

Since forever, Tuleap project administrators can trigger Jenkins jobs or generic webhook call when a push occurs on a Git repository. That’s convenient but when you have a lot of repositories in your project, it can be tedious to set up and hard to keep in sync.

The ambition of the Jenkins / Tuleap integration is to make your CI/CD setup one time and then forget it (well, as much as a CI/CD pipeline can be forgotten :cough: :cough:).

Starting Tuleap 11.12, the Jenkins Git triggers (the standard Git one and the Tuleap Branch Source one) can be set up at project level and will apply for all Git push made in any repository in your project.

As soon as the setup is done, the very next push made in the project will notify the Jenkins servers configured at project level. No need to change anything in your Jenkins file or Jenkins server configurations.

The feature is hidden behind a feature flag, you can activate it by setting $git_allow_jenkins_plugin_hook_configuration = 1; in your local.inc.

User account redesign

We regularly add options for user account management. The layout in the form of one-single-page was ok until it has become overstretched. It was time to refresh this area, all the more we will soon add another bunch of personal things to manage (thanks OAuth2 grants).

Preferences and account settings are now divided into tabs and grouped by topic or plugin. It should be easier to find the right information with this new organization.

Simplifying tracker creation (work in progress)

Creating a new tracker is not something that’s done often, but when it’s time to do it, it’s nice to have a slick UI, better guidance and streamlined flow.

You won’t be surprised to see the same pattern used for project creation (2 steps wizard). You will select your template on the first screen and give the name on the second one.

As mentioned in the title, it’s a work in progress so not all templates are available in this release. As of now you can pick-up templates from Template projects, XML files or start from empty. In the next release, you will be able to pick trackers from other projects.

Once the template is selected, you will enter the name of the tracker. As for projects, the technical short name of the tracker is automatically generated out of the name. The availability of the names are checked in real-time.

Once created, you are redirected to the administration page to finalize your tracker.