Soot Continuous Integration - Jenkins & Nexus

Image credit: Photo Pexels & Jenkins Logo

Finally, my colleague Manuel Benz and I migrated Soot’s build to Maven! Now, we pushed a valid and working pom.xml, including all required dependencies, to github.

Detailed instructions on how to use Maven to build Soot can be found here.

Migrating to Maven

Migrating Soot’s current Ant build to Maven required us to replace each Ant tasks successively with a corresponding Maven plugin/configuration.

First, we deployed all dependencies Soot requires to build onto our Nexus server, excluding all dependencies that are already deployed in Maven Central. Consequently, we could delete the lib folder in the repository and let maven resolve all dependencies.

Second, we had to replace the Ant XSL task with an appropriate configuration of the xml-maven-plugin to generate all Soot options and singletons properly during a build

Third, we had to generate the code for all test classes and include resource files in the resulting jar. The result of our work can be found here

Anyway, it is now possible to simply build a project against Soot including the following snippet in the project’s pom.xml.

    <name>soot snapshots</name>

Soot CI - Jenkins & Nexus

Manuel Benz installed and configured the Jenkins and Nexus server for Soot. Luckily, due to my previous experience with MechatronicUML’s build server, I could support him and we could set up the servers really fast.

He also configured Let’s Encrypt certificates!

Side Note: The let’s encrypt CA certificates are contained in Java versions >= 1.8.151 only. Using a prior Java version Maven cannot validate the certificates and throws an exception.

A nice feature of the Jenkins setup is that all pull-request can be built and tested flawlessly! A simple

ok to test


please retest this

is sufficient to trigger all Jenkins checks for the pull-request.

Thanks @Manuel Benz!