Difficulty: Beginner
Estimated Time: 10-15 minutes

In this scenario, you will quickly bootstrap a pipeline for a new app.

Adding a new pipeline for a known stack to the delivery system should be fast and not require error-prone manual intervention (copy/paste between jobs).

At the same time, by keeping everything configured as code, we guarantee that we can at any moment recreate a fully running delivery system - including our application pipelines!

We will use docker-compose to launch the delivery chain composed of Jenkins to build and test our example applications and Artifactory to store the resulting artifacts.

Once up and running, we should find the new pipeline running side by side with pre-existing ones.

Now let's get started!

Manuel Pais

In a short sequence of steps, we have built and launched a simple but complete delivery system.

All the necessary configuration was coded, allowing a full restore of Jenkins, including required plugins and job for our application.

Once Jenkins found the application pipeline definition (Jenkinsfile) in its repo, it launched the pipeline run without any manual intervention.

In short, with "everything as code" and a few commands we have been able to go from nothing running to a full delivery system with pipelines being executed!

Bootstrap a New Application Pipeline

Step 1 of 5

Create a new app repo in GitHub

Open GitHub and make sure you are logged in:

https://github.com

If you don't have a GitHub account, you'll have to create one before continuing.

Now create a new application repo by forking this existing repo:

https://github.com/SkeltonThatcher/spincast-todobackend

step1-fork-repo

For reference, here is the pipeline definition (Jenkinsfile) for the app we just forked:

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