This repository is to demonstrate skills in Vagrant, Ansible, and Jenkins. It simulates a very simple (and not very secure) build server using Vagrant or Docker Compose to supply a Linux Virtual Machine and Ansible to install and configure an HTTP instance of Jenkins and Artifactory and expose them on port 58080 and 58082 of the host machine.
If using the Docker Compose file the services are exposed on 8080and 8082.
To run using Docker Compose (requires Docker to be installed on the host machine) run docker compose up from the project root directory.
To run using Vagrant (requires Vagrant and a VM provider to be installed) run vagrant up from the project root directory.
The Vagrant or Docker Compose environments will automatically install Jenkins and configure the required plugins. On first login you will need to create an admin account as per the post installation steps defined here to make use of the server.
In order to demonstrate the ability to push build files to an artifact repository the OSS version of Artifactory is also deployed alongside Jenkins. It is exposed on port 58082 of the host machine and will need to be configured as per JFrog's documentation. The Jenkins Artifactory plugin should also be installed and configured with the server id set to 'ArtifactoryPlayground'.
Sadly the relevant REST API calls which could be used to automate the creation of the required repositories and users are not available in the OSS version of Artifactory. This means you will need to configure a generic local repository (generic-local) and a user with 'manage' permissions to that repository in order for the Jenkins pipelines referenced below to work correctly.
This username and password must match the credentials configured automatically by jenkins (jenkins/true-stint-free-mistaken) (obviously in production these would be nowhere near source control :D).
There are companion code repositories which contain example Jenkins pipelines which can be used with this playground.
- TBC
N/A
- TBC
N/A
Each of the projects can be added to Jenkins as a 'Pipeline' item. To test these examples create a 'Pipeline' item in Jenkins as per the instructions below.
- From the Jenkins 'Dashboard' select 'New Item' from the left hand nav menu
- Enter a name for your 'Pipeline', select 'Pipeline' from the list of item types, and then click 'Ok'
- Enter a description for your 'Pipeline', select the 'Discard old builds' checkbox, and set the maximum number of builds to keep to 3. This will keep the disk usage low, even though the projects are quite small.
- Under 'Build triggers' select the 'Build periodically' check box and leave blank. This will mean your build is never triggered but it will still work on demand.
- Under 'Pipeline' set your 'Definition' to be 'Pipeline script from SCM'. Then set your 'SCM' to be 'Git', copy the HTTPS clone link for the repo you wish to test, leave all other options as per the default, and save your pipeline
- You can now test your 'Pipeline' by selecting it from the Jenkins 'Dashboard' and clicking 'Build Now' from the left hand nav menu.
