Try it

Agent

Docker image (for the docker agent)

Language

Stages (comma separated)

One or more of: checkout, build, test, deploy.

Branch guard (optional)

Add a post/always block

File: Jenkinsfile
Stages: checkout, build
Content: # Generated in the browser — review this file and adapt it to your project before committing. pipeline { agent any stages { stage('Checkout') { steps { checkout scm } } stage('Build') { steps { sh 'npm ci' sh 'npm run build' } } } post { always { echo 'Pipeline finished' } } }

# Generated in the browser — review this file and adapt it to your project before committing.
pipeline {
  agent any

  stages {
    stage('Checkout') {
      steps {
        checkout scm
      }
    }
    stage('Build') {
      steps {
        sh 'npm ci'
        sh 'npm run build'
      }
    }
  }

  post {
    always {
      echo 'Pipeline finished'
    }
  }
}

Supported formats

Input: text
Output: text

Privacy

Runs entirely in your browser. Your input is never uploaded, stored, or sent to a third party.

Processing: In your browser
Privacy level: Browser only

Generated a declarative Jenkinsfile with 4 stage(s).

How it works

Declared the docker agent using node:20-alpine.
Emitted stages: checkout, build, test, deploy.
Guarded every stage with a branch condition for "main".
Added a post/always block.

The pipeline is a starting point: review the agent and steps for your Jenkins setup.
No credential is written into the file; bind Jenkins credentials in the UI.

Methodology

Emit a `pipeline {}` block with the selected agent declaration.
Emit each selected stage with an optional branch guard and the matching steps.
Append the optional post/always block and close the pipeline.

Usage

Choose the Jenkins agent and, for docker, the image.
Select the pipeline stages.
Run the generator and copy the result into a Jenkinsfile.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Docker agent with test and deploy

{
  "agent": "docker",
  "dockerImage": "node:20-alpine",
  "language": "node",
  "stages": [
    "checkout",
    "build",
    "test",
    "deploy"
  ],
  "branch": "main",
  "post": true
}

Example result

{ "filename": "Jenkinsfile", "content": "# Generated in the browser — review this file and adapt it to your project before committing.\npipeline {\n agent {\n docker {\n image 'node:20-alpine'\n reuseNode true\n }\n }\n\n stages {\n stage('Checkout') {\n when {\n branch 'main'\n }\n steps {\n checkout scm\n }\n }\n stage('Build') {\n when {\n branch 'main'\n }\n steps {\n sh 'npm ci'\n sh 'npm run build'\n }\n }\n stage('Test') {\n when {\n branch 'main'\n }\n steps {\n sh 'npm test'\n }\n }\n stage('Deploy') {\n when {\n branch 'main'\n }\n steps {\n sh 'echo \"Add your deployment command here\"'\n }\n }\n }\n\n post {\n always {\n echo 'Pipeline finished'\n }\n }\n}\n", "lineCount": 52, "sections": [ "checkout", "build", "test", "deploy" ], "stages": [ "checkout", "build", "test", "deploy" ] }

Plain agent with checkout

{
  "agent": "any",
  "dockerImage": "",
  "language": "none",
  "stages": [
    "checkout"
  ],
  "branch": "",
  "post": false
}

Limitations

Declarative vs scripted pipelines

The declarative pipeline uses a fixed `pipeline { agent; stages { … } post { … } }` structure. It is more constrained than the scripted Groovy form but is easier to review and less prone to accidental side effects.

The generator emits only declarative syntax and never interpolates an unchecked string into a shell step.

Frequently asked questions

What is a declarative pipeline?: Jenkins offers a declarative syntax (`pipeline { … }`) with a fixed structure of agent, stages and post blocks. It is stricter and easier to read than the scripted syntax, and it is what this generator emits.
Why is there no deployment command?: Deployment is environment-specific, so the deploy stage contains a clearly labelled placeholder you replace.

Sources

Jenkins Pipeline syntax (declarative) — Jenkins
Jenkins Pipeline documentation — Jenkins

Send feedback

Tell us if this tool helped, report a problem, or suggest a tool. Only the message you type is sent — never the input you used in the tool.

Was this tool useful?

Prefer to write to us directly? See the contact page.