Because we want to launch a fully working delivery system, we need to build customized docker images, in particular for Jenkins.

We can customize things like the Jenkins layout, which plugins to install, and, crucially, point Jenkins to the repo where our application's pipeline definition lives.

You can browse the "jenkins" folder in the editor to see the customization code.

When ready, run docker-compose build (this may take a few minutes to complete).

When finished, you can run docker images to find the newly built images: root_runtime, root_nginx, and root_jenkins.

We now have everything ready to launch the delivery pipeline.

Run docker-compose up -d (this may take a few minutes to complete as it pulls other necessary docker images that we will use but not build like we did for Jenkins).

Now click the "CI/CD Pipeline" tab, or follow this link:

https://[[HOST_SUBDOMAIN]]-80-[[KATACODA_HOST]].environments.katacoda.com/

You should see a dashboard listing the available tools (Jenkins and Artifactory):

While you read this, Jenkins should be checking the GitHub repo that we configured as containing our application's pipeline definition (Jenkinsfile):

https://github.com/SkeltonThatcher/spincast-todobackend/blob/master/Jenkinsfile

Now click on Jenkins from the "CI/CD Pipeline" dashboard or follow:

https://[[HOST_SUBDOMAIN]]-80-[[KATACODA_HOST]].environments.katacoda.com/jenkins

Eventually, you should see a green build for our application called todobackend-java. This might take a few minutes depending on the network connection. Make sure to refresh the page every few minutes (or click "Enable Auto Refresh" on the top right).

Finally, we can check that the artifact built by the pipeline has been correctly stored in Artifactory, an artifact management tool.

Click on Artifactory from the "CI/CD Pipeline" dashboard or follow:

https://[[HOST_SUBDOMAIN]]-80-[[KATACODA_HOST]].environments.katacoda.com/artifactory/webapp/#/

In Artifactory, search for all jars (*.jar) and you should find a spincast-todobackend-inmemory-1.02.jar artifact with path todobackend-java.

You can go back to Jenkins and cross-check that this was the artifact built by the pipeline!