Hi all,
I'd like to report a success building Eclipse aCute (typical Eclipse plugins built with Tycho and shipped as a p2 repo published on
download.eclipse.org) using a Jenkinsfile.
See
https://ci.eclipse.org/acute/job/aCute/ . This is actually a *multi-branch pipeline* job, the job is configured to look at the branches and PRs on GitHub repository, and provision a job for each branch and PR reading the Jenkinsfile. It seems to automatically trigger a build whenever it notices a change (the job is configured to look for changes every 15 minutes, but the "Scan repository now" option allows to trigger a check on demand)
Here is the current Jenkinsfile for aCute:
https://github.com/eclipse/aCute/blob/master/Jenkinsfile . While it looks easy, it was a bit painful to author; I have to admit I have some concerns with those Jenkins pipeline files which are extremely vague and hard to author and maintain; anyway this one works and may be used as example...
The only thing I didn't try to implement yet is the support for SonarQube analysis in the Jenkinsfile to get from time to time one build publishing reports there. It would probably be non-trivial to add in the Jenkinsfile as it would involve putting conditions in many place... If you feel interested to contribute that to aCute, that would be great, and it would be easy to reuse this result on many other Eclipse.org projects.
