GitLab CI Generator

Generated a GitLab CI pipeline with 2 stage(s).

How it works

• Declared the stages list: build, test.
• Set the pipeline image to node:20-alpine.
• Added a cache keyed by the commit ref.
• Emitted one job per stage referencing its stage.

• The deploy job is manual by default so it never runs unnoticed.
• The file is a starting point: review the image and commands before committing.

Methodology

1. Emit the `stages:` list in the canonical build/test/deploy order.
2. Set the pipeline `image` and the optional `cache` block.
3. Emit one job per selected stage with the matching commands and a `stage:` reference.

Usage

1. Choose the container image and language.
2. Select the stages the pipeline should run.
3. Run the generator and copy the result into .gitlab-ci.yml.

Examples

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

Node build and test

{
  "image": "node:20-alpine",
  "language": "node",
  "stages": [
    "build",
    "test"
  ],
  "cache": true
}

Python with deploy

{
  "image": "python:3.12-slim",
  "language": "python",
  "stages": [
    "test",
    "deploy"
  ],
  "cache": false
}

Limitations

How the generated pipeline is structured

GitLab runs one job per stage in the order declared by `stages`. Each generated job is a top-level key that names its stage and its scripts.

The cache block is only useful when the image's package manager writes to a predictable directory; edit the paths for your stack if needed.