https://github.com/stefanreichert/hello-jenkinspipelines
A simple example how to use Jenkins Pipelines to build and containerize a project
https://github.com/stefanreichert/hello-jenkinspipelines
docker docker-compose jenkins-ci jenkins-docker-pipeline jenkins-pipeline
Last synced: 6 months ago
JSON representation
A simple example how to use Jenkins Pipelines to build and containerize a project
- Host: GitHub
- URL: https://github.com/stefanreichert/hello-jenkinspipelines
- Owner: stefanreichert
- License: mit
- Created: 2019-05-24T08:30:37.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2019-05-31T09:25:06.000Z (over 6 years ago)
- Last Synced: 2025-04-30T16:07:53.783Z (6 months ago)
- Topics: docker, docker-compose, jenkins-ci, jenkins-docker-pipeline, jenkins-pipeline
- Language: Dockerfile
- Homepage:
- Size: 25.4 KB
- Stars: 1
- Watchers: 1
- Forks: 5
- Open Issues: 0
-
Metadata Files:
- Readme: Readme.MD
- License: LICENSE
Awesome Lists containing this project
README
# Hello Jenkins Pipelines
This projekt is a simple example how to use _Jenkins Pipelines_ to build and containerize a project, having the
infrastructure available as _Docker_ image as well. The project is based on _Java_/_SpringBoot_ and is packaged and
containerized with _Docker_.
## Infrastructure
The infrastructure is located in the folder ``/build-env``. The ``Dockerfile`` describes the Jenkins base Docker image
extended by _Maven_ and _Docker_ itself. _Maven_ is required to build the project, _Docker_ tooling is needed to build
and push the _Docker_ image.
The ``docker-compose-yml`` bundles the custom Jenkins image with the standard _Docker_ registry and a web frontend for
the registry.
## Project
The project itself is quite small, it just consists of a static page. To build the project, you may use
``mvn clean verify``. This will build, test, package and, for convenience, bundle the project with it's dependencies
in a single jar.
## Execution
### Run the infrastructure stuff
Simply execute ``docker-compose build`` to build the respective docker images and ``docker-compose up`` in the
``/build-env`` folder. Hello _Jenkins_ at ``http://localhost:8081``. You need to setup your Jenkins, please do as
you're told ;)
### Create a Jenkins project
Create a _Multi-Branch Project_ on your _Jenkins_ build server. Map the project to
``github.com:stefanreichert/hello-jenkinspipelines.git`` (or any other project you like...). Since the build server will use the ``Jenkinsfile`` no further configuration is required. Your project will automatically be built, the result will be pushed to your local _Docker_ registry at ``http://localhost:5000``. That's basically it...
### Watch the result
There is a registry UI deployed with the infrastructure. At ``http://localhost:8082`` you will find a web frontend
exposing your registry content. Your build results will show up here.
### Noteworthy
There will be state on your host machine...
* Jenkins home folder ``~/tmp/docker/jenkins/home``
* Maven home folder ``~/tmp/docker/maven/home``
In order to allow _Docker_ tooling inside a _Docker_ image, the _Jenkins_ images maps the _Docker_ socket file as volume to share the engine with the container. Seems to good practice ;)