jenkins-bootstrap-shared
configuration-as-code-plugin
Our great sponsors
jenkins-bootstrap-shared | configuration-as-code-plugin | |
---|---|---|
6 | 12 | |
323 | 2,636 | |
- | 0.6% | |
6.5 | 9.0 | |
6 months ago | 8 days ago | |
Groovy | Java | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jenkins-bootstrap-shared
-
Looking for a speaker on a panel on "how to make the most of Jenkins", pm me if interested
You can capture plugins and Jenkins versions using the script console to provision a second pristine Jenkins for additional testing like upgrade testing. I go deeper into this with complete immutable Jenkins infrastructure with jenkins-bootstrap-shared.
-
Steps to improve maintenance efforts
I recommend capturing your plugin versions. You can do it via maven or gradle. You could use the script console scripts on Jenkins. For testing upgrades you would need other means.
-
What is the best course/courses to learn pipeline as code with Groovy and Jenkins
Jenkins as immutable infra
-
How to safely upgrade jenkins plugin. What is the fail proof way to do it.
You can do this by script console yourself and use the community docker image. Alternately, you can try out jenkins-bootstrap-shared project I made which pulls Jenkins into a JKD8 container (I plan to upgrade it to OpenJKD11 since Jenkins now supports that).
-
How to use Jenkins the DevOps way in 2022
Here's how I have it scripted. (documentation : https://github.com/samrocketman/jenkins-bootstrap-shared/tree/main/scripts/upgrade )
configuration-as-code-plugin
-
Help! Confused about the relationship between Software Engineering and DevOps
First, developers could be taking care of maintaining the CI/CD tool.. As is (dev)ops will provide a running instance and everything from there is dev's responsibility, eg. Jenkins via https://plugins.jenkins.io/configuration-as-code/ .
- Jenkins CASC plugin
-
The only Jenkins Plugins you need
configuration-as-code https://plugins.jenkins.io/configuration-as-code/
- Fully scripted Jenkins server with terraform
-
Setting up a Jenkins instance with Configuration as Code (using yaml configuration)
Now we are going to use Configuration as Code plugin and some other plugins.
-
Why do y'all hate Jenkins? (What pipeline tools do you use?)
Looks like it does pretty much everything except install plugins ("We don't support installing plugins with JCasC" https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/README.md)
- Separate .yamls for Jenkins Configuration-as-Code
-
My School DevOps Project [part 1] - Jenkins
--- jenkins: numExecutors: 1 systemMessage: "Hi, jenkins setup with jcasc" securityRealm: local: allowsSignup: false # prevents anonymous users from creating an account through the web interface users: - id: ${JENKINS_ADMIN_ID} password: ${JENKINS_ADMIN_PASSWORD} authorizationStrategy: globalMatrix: permissions: #- "View/Delete:authenticated" #- "View/Read:authenticated" #- "View/Configure:authenticated" #- "View/Create:authenticated" - "Job/Read:authenticated" - "Job/Build:authenticated" - "Job/Configure:authenticated" - "Job/Create:authenticated" - "Job/Delete:authenticated" - "Job/Discover:authenticated" - "Job/Move:authenticated" - "Job/Workspace:authenticated" - "Job/Cancel:authenticated" - "Run/Delete:authenticated" - "Run/Replay:authenticated" - "Run/Update:authenticated" - "Overall/Read:admin" - "Overall/Administer:admin" crumbIssuer: "standard" # Docker: https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/docker clouds: - docker: name: "docker" dockerApi: dockerHost: uri: "unix:///var/run/docker.sock" templates: - labelString: "docker-agent" dockerTemplateBase: # TODO: pin sha256 or versions when using in production image: "jenkins/agent" remoteFs: "/home/jenkins/agent" connector: attach: user: "jenkins" instanceCapStr: "10" retentionStrategy: idleMinutes: 1 security: scriptApproval: approvedSignatures: - method java.lang.String indexOf int - method io.jenkins.plugins.casc.ConfigurationAsCode configure - staticMethod io.jenkins.plugins.casc.ConfigurationAsCode get tool: git: installations: - home: "git" name: "Default" jdk: installations: - home: "/opt/java/openjdk" name: "java" maven: installations: - name: "maven" properties: - installSource: installers: - maven: id: "3.6.2" jobs: - file: /var/jenkins_config/jobs/folders.groovy - file: /var/jenkins_config/jobs/jobs.groovy
-
Interesting Task
At my previous job the entirety of Jenkins was all in code. We would blow away our entire Jenkins instance and just copy/paste the config back into Jenkins and it would all be back. I believe that also had all of the configurations for the jobs as well. In that case, that could be ideal. If I remember correctly this was all done in Groovy and not using the Configuration as Code (YAML) plugin.
-
CMV: Jenkins shouldn't be anywhere near a robust, mature application environment
Most of the main plugins are configurable (here are some examples) and the rest you can configure via groovy. If there's good documentation, writing the groovy scripts is fairly easy too
What are some alternatives?
jenkins-script-console-scripts - A repository of one-off script console scripts for Jenkins.
job-dsl-gradle-example - An example Job DSL project that uses Gradle for building and testing.
Packer - Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
artifact-manager-s3-plugin - Artifact manager implementation for Amazon S3
blog - A personal technical blog. Full featured complete with automated peer review.
warnings-ng-plugin - Jenkins Warnings Plugin - Next Generation
groovy-guru - Groovy Intellisense for Visual Studio Code
pipeline - A cloud-native Pipeline resource.
jervis - Self service Jenkins job generation using Jenkins Job DSL plugin groovy scripts. Reads .jervis.yml and generates a job in Jenkins.
Design Patterns - Design patterns implemented in Java
pipeline-library - Collection of custom steps and variables for our Jenkins instance(s)
docker - Docker official jenkins repo