Jenkins CI Builds

Each bb4 respository has a Jenkins file at the root. The Jenkins file defines the steps of the CI build for each project. The pipeline is similar in each case and the general template is defined once in var/commonJenkinsPipeline.groovy.

To use Jenkins, follow these one time steps:

• Install and configure Jenkins locally or on a server.
• Create pipeline projects for each repository in Jenkins. Point it to the git repo, and specify the Jenkins file to build from.

Once Jenkins is running, any checkin to any repository should kick off a CI build and automatically run down-stream builds as well.

On Windows, there is a Jenkins service that needs to be running. Usually it starts automatically, but if http://localhost:8082/ is not accessible, check that it is running.

Jenkins needs access to your gradle.properties file with the credential information is so it can deploy artifacts to Sonatype. One way to do this (on Windows) is to put your gradle.properties file in C:\Windows\System32\config\systemprofile\.gradle.