Continuous Integration Tools Resources

Mostly Declarative pipeline since t makes the pipeline code easier to read and write. This code is written in a Jenkinsfile which can be checked into a source control management system such as Git. scripted pipeline uses stricter groovy based syntaxes. The declarative pipeline is defined within a block labelled ‘pipeline’ whereas the scripted pipeline is defined within a ‘node’. The Declarative pipeline code will looks like this: pipeline { agent none stages { stage('Example Build') { agent { docker 'maven:3-alpine' } steps { echo 'Hello, Maven' sh 'mvn --version' } } stage('Example Test') { agent { docker 'openjdk:8-jre' } steps { echo 'Hello, JDK' sh 'java -version' } } } } This also promotes the idea of a "Shared Libraries" pipeline: https://jenkins.io/doc/book/pipeline/shared-libraries/

Show More

Show Less

I think you can do it via tools like Chef / puppet, but building full cluster from the scratch may take significant time. Another option can be to dockerize the full solution. Option 3 can be keeping the Jenkins Server up all the time and load Slaves on demand (provide by clouds like Docker / Kubernetes / AWS etc. )

Show More

Show Less

Every commit triggers a single job by default. If two commits have been pushed on the Startup plan, they'll be run right away. Subsequent commits have to wait until the builds finished.

Show More

Show Less