If you need more specific configuration than this, use the following Dockerfile as a template.

File casc_configs/auth_config.yml is specifically to overwrite the base container.

You can add plugin configurations by adding one or more to jenkins-plugins.yaml and running /bin/jenkins-plugin-cli -f /path/to/jenkins-plugins.yaml.

Plugin files need to be in the format specified by the base jenkins/jenkins container and described in the Jenkins Docker README file.

The Configuration as Code (CasC) plugin is installed as part of the Jenkins Controller container and will read all configuration files out of the /usr/share/jenkins/ref/casc_configs/ directory. The CasC plugin docs have examples for how to configure many popular plugins.

Groovy scripts can be added to /usr/share/jenkins/ref/init.groovy.d/ to be run when Jenkins starts up. This is a good way to provide repeatable configuration if you need something outside of additional plugins or features coverered by the CasC plugin. Please note that scripts in this directory are run in alphabetical order so if you are relying on scripts from more than one layer of Docker images be sure to name your files appropraitely.

# Add in team specific groovy configs
ADD groovy_scripts/10_some_script.groovy /usr/share/jenkins/ref/init.groovy.d/

Contains:

GITHUB_API_TOKEN=<Your Token>

This image is used for local development, if you want a smaller container image you may remove ldap plugin from plugins/01_base_auth_plugins.txt and build again.

docker-compose up will give you a controller that can run docker jenkins agents using label docker-agent

# Example below from https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/demos/jenkins/jenkins.yaml#L63-L70A
# https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/integrations/src/test/resources/io/jenkins/plugins/casc/GlobalLibrariesGitHubTest.yml
unclassified:
  globalLibraries:
    libraries:
      - name: "<name your users will reference in @Library()>"
        defaultVersion: "<default branch to checkout>"
        retriever:
          modernSCM:
            scm:
              github:
                repoOwner: "<your GitHub Org name>"
                repository: "<your jenkins library repository name>"
                credentialsId: "github-api-username" // assuming you are using the default credentials

# Example below from https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/jobs
jobs:
  - script: >
      multibranchPipelineJob('<repository name>') {
        branchSources {
          github {
            // The id option in the Git and GitHub branch source contexts is now mandatory (JENKINS-43693).
            id('12312313') // IMPORTANT: use a constant and unique identifier
            scanCredentialsId('github-api-username') // assuming you are using the default credentials
            repoOwner('<your GitHub Org name>')
            repository('<repository name>')
          }
        }
      }

More at jenkins-job-dsl

• LTS Release Line
• LTS Changelog
• Jenkins LTS Upgrade Guide
• GitHub app authentication guide
• Using GitHub App authentication with checks API
• GitHub Apps Authentication & Checks API for Jenkins - Youtube video
• GitHub App Authentication and Checks API - Google slides