Modernize CI via Jenkinsfiles (part 1)

The Jenkins-based CI currently relies on old-fashioned scripts that must be edited in the Jenkins web UI or copy pasted back and forth from an editor. This is unwieldy and changes to the scripts are not traceable.

This task is about migrating the scripts used to Jenkinsfile so that they can be versioned along the code. This also has the benefit that testing modified jobs can be more easily done from the CLI via the jenkinscli tool.

changed the description

added SprintIn progress label

Current milestone: All packaging builds can be offloaded in parallel on all 'linux-builder' Jenkins nodes, which allows building most packages in less than 30 minutes.

Remaining tasks:

• 1. Replace current validation job by the new Jenkinsfile
• 2. Add stage for signing packages
• 3. Add stage for deploying packages to dl.jami.net
• 4. Replace packaging-deploy jobs by Jenkinsfile*

• Currently the Jenkinsfile accepts parameters to tweak its behavior; this won't be very convenient as it will require manual conf before running the job. It seems the way to go is to move the Jenkinsfile code to a shared Jenkins library, and define per-job Jenkinsfile that call to that shared library with the right parameters.

added SprintTo review label and removed SprintIn progress label

changed title from Modernize CI via Jenkinsfiles / library to Modernize CI via Jenkinsfiles (part 1)

I think I'll await feedback from those making the releases for what would be nice to have next; we can tackle any further improvements in future sprints; what we have now is already much better IMHO.

closed

A Jenkinsfile allowing to build all packaging targets in parallel (on multiple nodes) and deploy was with commit 27be9f5027. Closing.

added packaging label