GitLab CI Generator
Build a .gitlab-ci.yml from stages and jobs — images, scripts, artifacts, and branch rules.
Pipeline
Job 1
Job 2
.gitlab-ci.yml
image: node:20
stages:
- build
- test
build:
stage: build
script:
- npm ci
- npm run build
artifacts:
paths:
- dist/
test:
stage: test
rules:
- if: '$CI_PIPELINE_SOURCE == "push" && $CI_COMMIT_BRANCH == "main"'
script:
- npm test
Examples
Build then test
stages: build, test
job build (stage build): npm ci / npm run build, artifacts: dist/
job test (stage test, only main): npm teststages:
- build
- test
build:
stage: build
script:
- npm ci
- npm run build
artifacts:
paths:
- dist/Stages run sequentially; the test job is scoped to main via a rule and the build job exposes an artifact.
About this tool
The GitLab CI Generator turns a list of stages and jobs into a valid .gitlab-ci.yml file. You define the stages in order, set an optional default image, and add jobs with a stage, image, script, artifacts, and the branches they run on. The output is plain YAML you commit to your repo — nothing is uploaded.
How to use
List the stages
Enter stages like build, test, deploy in the order they should run.
Add jobs
For each job give a name, stage, image, script commands, artifact paths, and optional branch rules.
Copy and commit
Copy the .gitlab-ci.yml into your repo root and push — GitLab runs it on the next pipeline.
Use cases
New project bootstrap
Stand up a CI pipeline for a fresh repo without hand-writing YAML.
Branch-scoped deploys
Restrict deploy jobs to protected branches.
Common mistakes
Mistake:Forgetting the stage list.
Fix:Every job references a stage; list all stages up front or the pipeline errors.
Frequently asked questions
Related guides
Writing a Declarative Jenkins Pipeline
The structure of a declarative Jenkinsfile — agent, environment, stages with shell steps, and post actions — explained simply.
Bootstrapping a GitLab CI Pipeline
The shape of a .gitlab-ci.yml — stages, jobs, images, scripts, artifacts, and branch rules — and how they fit together.
Understanding a CircleCI config.yml
How version, jobs with Docker images and run steps, and workflows fit together in a .circleci/config.yml.
References & standards
Related tools
Reverse DNS (PTR) Lookup
Perform reverse DNS lookups for IPv4 and IPv6 addresses using DNS-over-HTTPS
MX Record Lookup
Inspect MX (Mail Exchanger) records, priority preferences, and email provider detection
TXT Record & SPF/DKIM Checker
Query TXT records and analyze SPF, DKIM, and DMARC email authentication security policies
NS Record Lookup
Inspect Name Server (NS) DNS records and authoritative DNS provider configurations
Jenkins Pipeline Builder
Build a declarative Jenkinsfile — agent, environment, stages with shell steps, and post actions
CircleCI Config Generator
Generate a .circleci/config.yml — jobs with Docker images and run steps wired into a workflow