ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #jenkins
Deciding between Docker, Kubernetes, SSH, or native agents in Jenkins impacts your pipeline's isolation and scalability. This guide compares the options and provides a Docker implementation.
Tired of copy-and-pasting pipeline code across projects? Learn how Jenkins Shared Libraries let you keep reusable logic in one place, version it, and keep your jobs lean.
The Declarative Pipeline `environment` directive introduced in Jenkins 2.5 is intended to define environment variables for downstream steps, but its handling varies between LTS releases such as 2.401 and 2.452. Goal: Verify whether the `environment` block reliably propagates variables to all pipeline stages across these versions, given reported inconsistenci
In a Declarative Pipeline, I need to display the build start time in a specific regional time zone (e.g., America/New_York) for a report generated later in the pipeline. The pipeline runs on agents with varying system time zones, and I want to avoid relying on the agent's local time; I prefer to use a pure Groovy solution within the pipeline script. I am uns
My JenkinsFile looks like: pipeline { agent { docker { image 'node:12.16.2' args '-p 3000:3000' } } stages { stage('Build') { steps { sh 'node --version' sh 'npm install' sh 'npm run build' } } stage ('Deliver') { steps { sh 'readlink -f ./package.json' } } } } I used to have Jenkins locally and this configuration worked, but I deployed it to a remote server
The retry(N) step in Jenkins Pipeline is designed to re-execute a block of code upon failure. However, this mechanism does not track side effects or state changes that occurred during previous attempts within the same block. When integrating Jenkins with external systems—such as REST APIs or databases—a failure occurring after a write operation but before th
The goal is to run integration tests that require a secret token without pulling in production credentials. The Jenkins Credentials Binding plugin offers withCredentials blocks that can bind SecretText and File types to environment variables or temporary files. In scripted pipelines, I need the secret token as a file for a downstream script, but the plugin o
Jenkins LTS 2.361.1 enforces a Java 11+ baseline, which shifts the toolchain origin for Docker agent builds and alters plugin compatibility boundaries. The JCasC plugin expresses controller settings as YAML, but its symbol coverage is incomplete, leaving certain plugin configurations exposed to manual adjustment. Meanwhile, the plugins.txt mechanism pulls ex
Goal Reduce idle infrastructure costs for a sporadic Jenkins workload by using the Docker Pipeline plugin to spin up temporary agents only when builds run. Constraints & Uncertainty Choosing the underlying Docker host—local Docker daemon, Docker Swarm cluster, or Kubernetes—affects scalability, isolation, and operational overhead. The plugin does not aut
kubernetes