Skip to content

Infrastructure (i.e. a dockerized Jenkins) and overview for the Jenkins Pipes demo

Notifications You must be signed in to change notification settings

tknerr/jenkins-pipes-infra

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 

Repository files navigation

Jenkins Pipes Infrastructure

This is meant to be a minimal example showing how to set up Jenkins 2.x with the Pipeline Plugin to support the following scenario:

Run It

Create the docker image and run it, with port 8080 forwarded to the host:

$ docker build -t jenkins-pipes .
$ docker run -it --rm -p 8080:8080 jenkins-pipes

Once Jenkins is started you should see at least the seed-job on http://localhost:8080.

If it has not run yet, simply trigger it and see how the actual jobs get created.

How it works

It's simply a minimalized jenkins (master only) setup that is running in a docker container. Looking at the Dockerfile you can see that all it does is:

  • inherits from the official jenkins:2.32.2 image
  • skips the setup wizard and leaves jenkins unsecured
  • installs the minimum necessary Job-DSL, Git and Pipeline plugins
  • copies the seedJob.xml to the Jenkins jobs directory

Optionally, you can pass the --build-args jobs_repo=... parameter to configure the seed job with your own jobs repository.

Where to go from here?

Now that you have a basic setup running, there are a few things to explore next:

  • create your own jobs repo and pass it via --build-args to to the docker build command
  • use docker-compose to set up the Jenkins master with a build slave that can build projects with your toolchain of choice (e.g. java / maven)
  • create a new hello world example for the toolchain of your choice and make sure it builds on your new build slave
  • ...

About

Infrastructure (i.e. a dockerized Jenkins) and overview for the Jenkins Pipes demo

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published