All tools / DevOps & infrastructure
Jenkins pipeline generator
Build a declarative Jenkinsfile with the agent, stages, credentials and notifications you need, and see which plugins it relies on.
1. Project and agent
2. Options and triggers
3. Stages leave a field empty to skip that stage
4. Docker image and deploy
Plugins this pipeline uses
Before you run it
Common questions
Where does the Jenkinsfile go?
Commit it as Jenkinsfile in the root of your repository. Then create a Multibranch Pipeline job in Jenkins pointing at the repository; it finds the file on every branch and pull request.
Why does the build fail with EACCES or permission denied in a Docker agent?
Jenkins runs the container as its own user, whose home folder is not writable, so npm, pip, Maven, Go and Gradle cannot write their caches. The generated file points those caches into the workspace, and uses a virtualenv for Python, which avoids the problem.
Why do the Docker and deploy stages use a different agent?
Build images like node or maven do not include the docker CLI, kubectl or ssh. Those stages run on an agent with that label, which you set up once with Docker installed. If you use "Any agent", everything runs on the same machine.
How are secrets handled?
Passwords, SSH keys and kubeconfigs are stored as Jenkins credentials and referenced by ID. Shell commands use single-quoted Groovy strings, so secrets are expanded by the shell and never written into the build log by Groovy.
Is anything sent to a server?
No. The Jenkinsfile is generated in your browser.