Declarative vs Scripted Jenkins Pipelines: Decision Guide
A decision guide comparing Jenkins declarative and scripted pipelines covering syntax version constraints and migration path with a minimal Jenkinsfile validation step.
Loading…
ReadMeFeed / Community knowledge
#jenkins-pipeline
Real questions. Useful conversations. Find the people who know your stack.
Jenkins Pipeline Shared Libraries: Architecture Note for Centralized Pipeline Policy
Centralize Jenkins pipeline logic with a version-pinned shared library while keeping controller trust boundaries explicit and operational checks in place.
jenkinsJenkins Builds Stuck 'Waiting for Next Available Executor' While Agents Look Connected
Pipeline builds stuck in the Jenkins queue while agents show as connected is a scheduling mismatch, not a connectivity problem. A diagnostic table, ordered checks, and fixes tied to each finding.
Jenkins Pipeline and External API Integration: Idempotency during retry(N) execution
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
Jenkins Pipeline docker agent and Docker daemon: image pull policy and host dependency reproducibility
Integration boundary The agent { docker { ... } } directive in Jenkins Pipeline delegates container provisioning to the Docker daemon available on the selected agent. This creates an integration boundary between the Jenkins controller's pipeline execution model and the host-level Docker runtime, where reproducibility depends on factors outside Jenkins' direc
dockerDoes Jenkins Pipeline CPS cache invalidate on shared library update without restart?
Jenkins compiles and caches Groovy scripts from Pipeline definitions and shared libraries to avoid re-parsing on each build. The cache is stored under $JENKINS_HOME/caches and is used by the Pipeline CPS plugin. The documented control for this behavior is the system property org.jenkinsci.plugins.workflow.cps.CpsThreadFactory.disableCache, which can turn cac
Build aborts at withCredentials when duplicate credential IDs span system and folder stores
A Jenkins Pipeline using withCredentials fails the build when a referenced credential ID cannot be resolved by any provider. The unresolved behavior concerns duplicate IDs: the same identifier can exist in the system store, a folder store, and a user store. In that situation, the binding step completes rather than aborting, but the value actually injected de
kubectl exec fails with the error "Unable to use a TTY - input is not a terminal or the right kind of file"
I am running a jenkins pipeline with the following command: kubectl exec -it kafkacat-5f8fcfcc57-2txhc -- kafkacat -b cord-kafka -C -t BBSim-OLT-0-Events -o s@1585031458 which is running fine on the terminal of the machine the pipeline is running on, but on the actual pipeline I get the following error: "Unable to use a TTY - input is not a terminal or the r
kubernetes