Continuous Integration

The Continuous Integration service in Tuleap allows you to link Jenkins jobs to your project and monitor build statuses directly from the platform. It also supports automatic build triggering after commits to your SVN repository.

Information

This service is historically focused on SVN. For a complete Git/Jenkins integration — including automatic discovery of repositories and branches, pull request build status, and test automation results — refer to the technical Tuleap CI documentation.

Prerequisites

• The Continuous Integration service must be enabled in the Project Administration (Services section).

• Only project administrators can add, edit, or delete jobs.

• The Jenkins server must be reachable from the Tuleap server.

Service page

Click the Continuous Integration link in the project navigation. The page displays the list of registered jobs with, for each one:

• a status icon for the last build (success, failure, in progress, not built),

• the reference and date of the last successful build,

• the reference and date of the last failed build,

• an RSS link to the build feed.

Add a job

1. Click Add job.

2. Fill in the fields:

   • Job URL (required): Full URL of the Jenkins job. Examples:

   • Trigger a build after commits (optional): see Trigger a build after an SVN commit.

   • Token (optional): Jenkins security token if the build trigger is protected by authentication.

3. Click Submit.

Information

Tuleap contacts Jenkins at registration time to automatically retrieve the job name. The Jenkins server must therefore be reachable from Tuleap when adding the job.

Edit a job

1. On the job row, click Edit.

2. The available fields are the same as when creating a job, with one addition:

   • Job name: Short name used for Tuleap cross-references (e.g. job #MyJob). Spaces are not allowed — they are automatically replaced by _.

3. Click Update job.

Delete a job

1. On the job row, click Delete.

2. Confirm the deletion in the modal.

Information

Deleting a job in Tuleap only removes the link between the project and the job. It does not delete the job in Jenkins.

Trigger a build after an SVN commit

When the SVN option is checked on a job, Jenkins is automatically notified after each commit to the project's SVN repository.

• By default, every commit triggers a build.

• You can restrict triggering to specific paths in the repository (one path per line in the dedicated field).

If a token has been configured in Jenkins to protect the build trigger, enter it in the Token field of the form.

Warning

Warning: The Git option in this form is deprecated since Tuleap 8.14. To trigger Jenkins builds from Git, use the webhooks configured in the Git service administration of your project. See the technical Tuleap CI documentation.

Cross-references to Jenkins

Tuleap automatically generates cross-references to Jenkins jobs and builds. You can use them in artifact comments, commit messages, or pull request descriptions.

Reference a job:

• job #JobName — job in the current project

• job #project-name:JobName — job in another project

Reference a build:

• build #175 — build #175 (only if a single job is configured in the project)

• build #JobName/175 — build #175 of job JobName

• build #project-name:JobName/175 — build in another project