Jenkins continuous integration (CI) jobs and configuration

[slarse]

The Jenkins jobs running over here test the latest snapshot of Spoon on a variety of projects, in a variety of ways. There are two general kinds of jobs:

• For projects that use Spoon
  • Inject the latest Spoon snapshot and run project's test suite
  • Uses the new inject_spoon_snapshot.py script
• For projects that don't use Spoon
  • Parse and pretty-print the project with spoon-maven-plugin using the latest Spoon snapshot
  • Then run the project's test suite

There's a bunch of tiny details surrounding this as well. In order to facilitate for someone else to manage Jenkins (or just myself next week when I've forgotten all about this), we should 1) streamline the jobs to make it very easy to add a new one, and 2) properly document how everything works.

[monperrus]

FTR, Jenkins nodes sos-builder01 (aka Ubuntu 16) now has Java 11 under '/usr/lib/jvm/java-11-openjdk-amd64/'

$ /usr/lib/jvm/java-11-openjdk-amd64/bin/java -version
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)

Installed from https://download.java.net/java/GA/jdk11/9/GPL/openjdk-11.0.2_linux-x64_bin.tar.gz

[monperrus]

FYI, https://ci.inria.fr/sos/job/Spoon-Snapshot-Deployer/ is now configured with Java 11

Ref: https://github.com/SpoonLabs/spoon-ci-config/commit/e14f7f709d4f7706375140a43deb69cb8355141e

[monperrus]

@seintur the full disk on sos-builder02 issue is solved, there were hundreds of temp dirs in /tmp/.

For some reasons, df reported incorrect free space.

[monperrus]

FYI, removed outdated certificate DST_Root_CA_X3.pem (Digital Signature Trust Co., CN = DST Root CA X3) on sos-builder01, which resulted in failing to curl

curl https://spoon.gforge.inria.fr/jenkins/build.sh
curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

Reference: https://www.stephenwagner.com/2021/09/30/sophos-dst-root-ca-x3-expiration-problems-fix/

[monperrus]

FTR, added GPG key to both nodes sos-builder01 and sos-builder02 in /buids/.gnupg/ (no passphrase) for cases when signing is used in the build.

[monperrus]

FYI, the Jenkins CI agent nodes (sos-builder01 and sos-builder02) now have 4GB of RAM.

[monperrus]

FTR, per https://github.com/INRIA/spoon/pull/4955#issuecomment-1276639549:

• Created an environment called “SBOM-store”
• In that environment, added a new secret with name “SBOM_DEPLOY_SSH”, and the value being the private SSH key

cc/ @siberov

[monperrus]

Btw, ci.inria.fr/sos seems to only show builds if you are logged in — and I don't believe I have an account :)

@I-Al-Istannen that's strange before it was public. you can simply create an account on https://ci.inria.fr/sos/ and I'll add you as member.

[I-Al-Istannen]

The jenkins instance has public user registration disabled @monperrus. I assume it shows more for you than this? It used to, I am pretty sure. I think you need to do some fiddling with access control beyond "grant read access to anonymous users" to make jobs show up. The user list is public though :^)

[monperrus]

Sign up on https://ci.inria.fr/ and tell me the email address you used so that I add you.

[I-Al-Istannen]

spoon-ci <ät> ialistannen.de

[monperrus]

added you!

[monperrus]

for the record, installed OpenJDK 17 and Maven 3.9 on both Jenkins nodes (sos-builder01 and sos-builder02).

resuscitated much of the CI jobs there, with some more changes, see https://github.com/INRIA/spoon/pull/5910