Making use for Jenkinsfile we can ignore jenkins state and spin new instance when required

We can either use stock jenkins/jenkins:lts required plugins will be installed on compose up

docker-compose up

If we use Dockerfile we'd be installing (extra + required) plugins on build stage

We have all default jenkins/jenkins env vars

AND

PROJECT_GIT specify a project git repo which would be added to jenkins automatically from init.d/job.groovy (optional)

PROJECT_NAME project name (optional) default=Project Name if PROJECT_GIT specified

PROJECT_BUILD if true jenkins will load project branches and build automatically

PROJECT_PLUGINS any extra plugins to be installed on jenkins init

example

      - "PROJECT_GIT=https://github.com/hasnat/stateless-jenkins.git"
      - "PROJECT_NAME=Stateless Jenkins"
      - "PROJECT_BUILD=true"
      - "PROJECT_PLUGINS="

So we're not depending on one jenkins, jenkins home don't matter, no back ups needed for jenkins, testing jobs...

We're using https://github.com/miyajan/jflint

for this repo we can use

jflint --csrf-disabled ./Jenkinsfile

Use following to listen changes on playground and run build in local jenkins

cd projects/playground
git init
git add .
git commit -m "one-commit"
npm install -g watch
watch "clear && git add . && git commit --amend <<< :wq && jflint --csrf-disabled ./Jenkinsfile" . -d

in docker-compose file mount your project directory to show up as project, add it to master and slave if working with slave making changes to this would force docker-compose to recreate jenkins containers

volumes:
  - "/path/to/your/project/on/host/some-project-name:/usr/local/jenkins-projects/some-project-name"

References:

https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/getting-started

https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md

https://jenkins.io