A Dockerized Jenkins CI-CD system for Concordia
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
ecentricsgr 7fb7982368 fix: remove forgotten volume 4 years ago
env refactor: add multiple virtual hosts 4 years ago
jenkins refactor: update plugins list 4 years ago
nginx-reverse-proxy-confs fix: move redirect confs to vhost for all services 4 years ago
utility-scripts Add groovy script for git credentials configuration 5 years ago
volumes Work on sonarqube, auto configuration, Add installation script, Add utility to update plugins 5 years ago
.dockerignore Add .dockerignore 5 years ago
.gitignore Update plugins.txt 5 years ago
LICENSE.md Update LICENSE.md 5 years ago
Makefile refactor: minor fixes 4 years ago
README.md refactor: update job name and webhook 4 years ago
SETUP.md Update plugins list 4 years ago
docker-compose.yml fix: remove forgotten volume 4 years ago

README.md

Janus

A Dockerized Jenkins CI-CD system for Concordia

Janus is a Docker image that contains an instance of Jenkins with all the necessary configuration built into it for handling the CI-CD of Concordia.

Prerequisites

Only needs a working installation of Docker.

Installation

The credentials of the default admin user created are passed to Jenkins using docker secrets. The files containing the username and password to be used can be found at the paths ./jenkins/secrets/adminUsername and ./jenkins/secrets/adminPassword respectively. Edit the files to change the default username and password.

The image also sets up a credential for use with docker when pushing images to docker hub. The username and password used can be found at the paths ./jenkins/secrets/dockerhubUsername and ./jenkins/secrets/dockerhubPassword respectively.

Then run:

make build
make run

During the Docker image build, a key-pair is created for usage with Gitlab. Get the public ssh key using:

make print-ssh-key

Then, on Gitlab, add the public key to the deploy keys of the project.

Jenkins also needs an access token from Gitlab to update build statuses. Create an access token and add it to Jenkins under Global Credentials.

Lastly a Webhook must be added to Gitlab, pointing to the Jenkins project. On Gitlab, navigate to the Webhooks menu in the Settings of the project and add a new webhook pointing to https://jenkins.ecentrics.net/project/concordia-multibranch-pipeline.

To get the git branches and Jenkinsfiles from each branch initiate a Multibranch Pipeline Scan.

In the SETUP you can find more details about the setup process, the credentials, plugins and other configuration that is done automatically and how to change these.

Contact

Apostolof – apotwohd@gmail.com
Ezerous - ezerous@gmail.com

Distributed under the MIT license. See LICENSE for more information.