pmsipilot-jenklab-ci

Jenklab CI

A command-line bridge between Gitlab CI and Jenkins CI.

Why?

Sometimes your CI is spread between Gitlab CI and Jenkins. Using a single UI to follow all your jobs is better than switching between two of them.

Gitlab has a nice UI for pipelines, it better than Jenkins' one.

This utility will let you trigger Jenkins jobs right from Gitlab pipelines. It will also forward the whole Gitlab CI environment to Jenkins as build parameters.

You will be able to see the whole build log direclty from Gitlab CI.

Usage

Jenklab CI is accessible through a command-line script:

 bin/jenklab-ci 
 
   pmsipilot-jenklab-ci 1.0.0 - A command-line bridge between Gitlab CI and Jenkins CI
     
   USAGE
 
     jenklab-ci build <job>
 
   ARGUMENTS
 
     <job>      Job name      required      
 
   OPTIONS
 
     --https                    Use https                optional      default: false
     --host <host>              Jenkins host name        optional                    
     --port <port>              Jenkins port number      optional      default: null 
     --username <username>      Jenkins username         optional                    
     --token <token>            Jenkins token            optional                     
 
   GLOBAL OPTIONS
 
     -h, --help         Display help                                      
     -V, --version      Display version                                   
     --no-color         Disable colors                                    
     --quiet            Quiet mode - only displays warn and error messages
     -v, --verbose      Verbose mode - will also output debug messages

A Docker image is also available to let you add it to your .gitlab-ci.yml:

stages:
    # ... 
    - jenkins
    
jenkins-job-name:
    image: pmsipilot/jenklab-ci
    tags:
        - swarm
    stage: jenkins
    when: manual
    script:
        - jenklab-ci build $CI_BUILD_NAME

Caveats

• Jenklab CI will stream the Jenkins build log to the Gitlab CI console: this can lead to huge logs stored in your Gitlab database.
• Your Jenkins job might take longer due to the time spent in queue. By default, Gitlab CI jobs are killed after 60 minutes. You might need to change the job timeout in you Gitlab project's CI/CD configuration.