eficode-academy / jenkins-katas Goto Github PK

View Code? Open in Web Editor NEW

3.0 4.0 199.0 896 KB

License: MIT License

Dockerfile 7.09% Java 48.90% Shell 34.00% Python 10.01%

jenkins-katas's Introduction

Jenkins Kata

Look into the labs folder for exercises

Open in google cloud shell

Spin up the Jenkins server by running: docker-compose up -d Jenkins is running on port 8080

Username: admin Password: 7p4rk3r4qgp3c2020 without 2020

Layout of this repository

.
├── app             # The application itself
├── ci              # Folder for all the ci specific files
├── component-test  # Python component test and setup
├── examples        # Examples of the different exercise solutions and more.
├── img             # Images for the readmes in the labs folder
├── labs            # All different exercises in Jenkins
└── setup           # Setup of jenkins.

jenkins-katas's People

Contributors

Stargazers

Watchers

Forkers

mortench3000 michaeldepner atombrella bicschneider km5tz jrrimbach an-tei marlemops leo68lej andreasbraesigk rainettzimmer kheider-maker ipfeiffer pn226 malthui michaelin johnding1995 banafshr zanderhavgaard pietarie anttirastas kumisopuli venetastefanova schiluveri anildbee2 sofielouise stenshoj mhtn cmc142 kaslangg mkorsgaard thegarne stef-r michaeldk12345 petbin githubanders bosch-eficode neethu-philip christoffernissen madslb omvk97 smiteyjonawar hoodedgull oskarskak maltebuk em135 thphr wolder prikx emiljohansen phols irusvind benz56 xitric danielvs1234 hrholm nicolaigram euronames henriksen89 thomasfr89 sieben8nein bnjmlnk nibug nicolai449 horib mathiasbrix mabar16 mathn16 mforberg emiltang danielszenczi sbangslund vicle18 babuskah emilkolvigraun jakobgamborg arian471 drunkduckling k3et sharanka itsmebenpax arkaria fcbfreak olnor18 simonmdsn jorgebaezgarrido freyacoded lpesola kargamborgh adamchabin saarajulia efigaja jacquesshield jerere coderamblings shannow13 safaie vsalomaki lal4tech vipotin

jenkins-katas's Issues

Replace image on creating host agent

Image in host shows different key host verification than what you should do

Make a section where people Sanity check on agents (go into logs)

In the create agents

Jenkins docker agent not executing correctly

While teaching Jenkins using this kata, multiple students confronted an issue where agents defined as docker containers would not execute.

The problem was persistent throughout different OS's and environments: some were running Vagrant (VirtualBox) on Windows, some Docker Desktop on Windows or macOS.

I personally could not reproduce the problem. My environment was running Jenkins on Docker Desktop (Windows) and everything worked as expected.

Only consistent messages that showed in the logs every time the problem occurred was

...
Jenkins does not seem to be running inside a container - -
...

while everywhere where things worked, the corresponding log-entry was

[Pipeline] sh
+ docker inspect -f . gradle:6-jdk11
.
[Pipeline] withDockerContainer
Jenkins seems to be running inside container 7886fea1c6ff2c3c59dba72500f73d00693fc64e06b600635c16c5ec8d76e2f2
$ docker run -t -d -u 0:0 -w /var/jenkins_home/workspace/jenkins-katas_master@2 --volumes-from 7886fea1c6ff2c3c59dba72500f73d00693fc64e06b600635c16c5ec8d76e2f2 -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** gradle:6-jdk11 cat
$ docker top 58d0ce76181245e4e5a72a3f93718ce18da85a00a159d4ea3d5b78ede3012854 -eo pid,comm

Multibranch pipeline does not scan for changes by default

We have to add to exercise 1 or 2, that students should go and enable periodic scan of repository in the "old" Jenkins UI. If not, their commits will not automatically trigger a build.

Either add it as an optional to the exercise, or add a slide and show it to the students.

Jenkins swarm agent fails in dind scenario.

Working:

pipeline {
  agent any
      
  stages {
    

   stage('Parallel execution') {
      parallel {
        stage('build app') {
          
          steps {
            sh 'echo hello world'
          }
        }
        stage('build app2') {
          
          steps {
            sh 'echo hello world'
          }
        }        
        stage('build app3') {
         
          steps {
            sh 'echo hello world'
          }
        }        
        stage('build app4') {
          
          steps {
            sh 'echo hello world'
          }
        }        
        stage('build app5') {
          
          steps {
            sh 'echo hello world'
          }
        }
        stage('build app6') {
          
          steps {
            sh 'echo hello world'
          }
        }
      }
    }

  }
}

Not working:

pipeline {
  agent any
      
  stages {
    

   stage('Parallel execution') {
      parallel {
        stage('build app') {
          agent {
            docker {
              image 'debian'
            }
          }
          steps {
            sh 'echo hello world'
          }
        }
        stage('build app2') {
          agent {
            docker {
              image 'debian'
            }
          }
          steps {
            sh 'echo hello world'
          }
        }        
        stage('build app3') {
          agent {
            docker {
              image 'debian'
            }
          }
          steps {
            sh 'echo hello world'
          }
        }        
        stage('build app4') {
          agent {
            docker {
              image 'debian'
            }
          }
          steps {
            sh 'echo hello world'
          }
        }        
        stage('build app5') {
          agent {
            docker {
              image 'debian'
            }
          }
          steps {
            sh 'echo hello world'
          }
        }
        stage('build app6') {
          agent {
            docker {
              image 'debian'
            }
          }
          steps {
            sh 'echo hello world'
          }
        }
      }
    }

  }
}

Reason is some kind of sketchy docker in docker part :(

Change post step from allways to clean-up

Clean up is the last post step that will be executed, and therefore we should move our "deletedir" to that.

Enhance 02-editing #test-reporting

Test reporting:
https://github.com/eficode-academy/jenkins-katas/blob/master/labs/02-editing-your-pipeline.md#test-reporting
Add an image of how the build stages works

Read through the PR based workflow exercise

Confusing wording: PR based workflow exercise.

Use master instead of new branch in 01-making-first-pipeline.md

Enable the use of JCasC for better user feeling

Unable to start Jenkins in Google Cloud Shell

Running docker-compose up -d in Google Cloud Shell leads to the following error:

michael_ingeman_nielsen@cloudshell:~/jenkins-katas/setup$ docker-compose up -d
Creating network "setup_default" with the default driver
Creating volume "setup_jenkins_home" with default driver
Pulling jenkins (praqma/jenkins-kata-jenkins:latest)...
latest: Pulling from praqma/jenkins-kata-jenkins
3192219afd04: Pulling fs layer
17c160265e75: Pulling fs layer
...
Status: Downloaded newer image for praqma/jenkins-kata-jenkins:latest
Building swarm_agent
ERROR: gcloud failed to load: /tmp/_MEITOPJ2m/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /usr/lib/python3.7/lib-dynload/_ssl.cpython-37m-x86_64-linux-gnu.so)
...
docker.errors.DockerException: Credentials store error: StoreError('Credentials store docker-credential-gcloud exited with "".',)
[15137] Failed to execute script docker-compose
michael_ingeman_nielsen@cloudshell:~/jenkins-katas/setup$

There are existing issues on this here and here. A workaround is described in the issue: Running export LD_LIBRARY_PATH=/usr/local/lib in the Cloud Shell before building works for me, but really shouldn't be necessary.

Make the IP section of agents more robust

Find a better way to find the IP address of the host inside docker

Minimum requirements when manually installing a Jenkins server

I've tried running the katas on a Jenkins instance installed using apt. There are a few prerequisites that might be worth mentioning in setup-on-your-own.md.

Docker must be available on the server and/or worker instance
The user running Jenkins ("jenkins" user by default) must be added to the Docker group
Ensure the Blue Ocean plugin is installed. It isn't installed by default or as part of the recommended plugins in a manually installed Jenkins instance.