cnp-jenkins-docker

Jenkins docker image

Testing locally

You need to checkout the cnp-jenkins-config and place it next to the cnp-jenkins-docker repo i.e.

$ ls cnp-jenkins-
cnp-jenkins-config/  cnp-jenkins-docker/

Run ./bin/bootstrap-secrets.sh cftsbox-intsvc, which will fetch the secrets required from the sandbox key vault.

Then run docker-compose up -d

A fully automated Jenkins image will be spun up exposed on port 8088 The credentials to login are admin/admin

The config is pulled from cac-test-local.yml, environment variables set in docker-compose.yml and organisation config in cnp-jenkins-config/jobdsl/organisations.groovy

Updating Jenkins

We run Jenkins in a docker container running on Kubernetes.

All configuration is managed in cnp-flux-config, there's common configuration and per-instance configuration.

The Jenkins image is built from this repo, after a pull request is merged an ACR task will automatically build and publish an image.

Jenkins Plugins

Plugins should be automatically updated by a combination of renovate and a GitHub action running the plugin-installation-manager-tool.

If you need to manually update plugins you can use:

./bin/update-plugins.sh
# or without docker
./bin/update-plugins-no-docker.sh

Rebuild the Jenkins container docker-compose up --build.

Check that Jenkins starts up, you can log in, and there's no errors on the 'Manage Jenkins' page about plugins failing to load.

Create a PR with the change

Jenkins Controller

Normally dependabot will create a PR automatically (#42), you can approve it and it will be automatically merged.

If you need to do it manually:

Update the FROM statement in the Dockerfile to the latest version.

Follow testing locally, check that it starts up, you can log in, and there's no errors on the 'Manage Jenkins' page about plugins failing to load.

Promoting a new Jenkins image

Create a pull request with your change in this repo.

After the PR is merged you can monitor the GitHub action build waiting for it to complete.

You can either check the GitHub action log in the 'Build and Push step' to find the new tag or run the below script:

az acr repository show-tags -n hmctspublic --repository jenkins/jenkins --subscription DCD-CNP-PROD --orderby time_desc --query "[?\!starts_with(@, 'pr')] | [0]" -o tsv

Update the tag in cnp-flux-config jenkins.yaml.

Only merge the PR for prod Jenkins very early in the day, or in very quiet times, it can take ~15 minutes to startup sometimes, likely due to the number of jobs and the number of traffic that it gets which slows down the startup.