Generate CI/CD configs for GitLab CI, CircleCI, Jenkins, and Travis CI with template stages.
Generate a build pipeline config for GitLab CI, CircleCI, Jenkins, or Travis CI from a few selections. You pick the target, choose stages such as build, test, and deploy, and type the command each stage runs; the tool assembles a single file in that system's own syntax. The usual surprise is that the four systems share the same stage vocabulary but not the same format: output for one is meaningless to the others, and switching providers means generating again, not reusing the file. Everything runs in the browser; the commands you paste never leave your machine. The result is a syntactically valid scaffold ready for real commands.
A concrete input and expected output from the current implementation.
Input
Target: GitLab CI Stages: build, test Build script: pip install -r requirements.txt Test script: pytest
Expected output
stages:
- build
- test
build:
stage: build
script:
- pip install -r requirements.txt
test:
stage: test
script:
- pytest A GitLab CI config is YAML: a top-level stages list fixes the run order, and every job declares a stage plus a script list. The generator maps each chosen stage to one job with that stage name and places the command you typed for it under the job's script key.
The tool holds a skeleton for each target and inserts your choices into it. For GitLab CI the skeleton is a stages list plus one job block per stage; each job carries a stage key naming its phase and a script list holding the commands you typed. Jobs appear in the order you selected their stages.
The four outputs do not share a format. GitLab CI and Travis CI are YAML but with different shapes: GitLab nests commands in per-job script lists, while Travis CI's legacy lifecycle puts them in top-level install and script keys and its jobs/include matrix form keeps them in per-job script keys under a named stage. CircleCI 2.1 is YAML with jobs, steps, and a workflows section. Jenkins is a Groovy Jenkinsfile wrapping stages in a declarative pipeline block. The same stage choices render four structurally different files.
No. It generates from templates; it does not parse files you already have, so you re-enter the stage names and commands yourself. Even the stage skeleton transfers imperfectly: provider-specific features such as caches, artifacts, matrix builds, and environment-scoped secrets have no direct equivalent in the other systems and must be recreated by hand.
Only at the level of syntax. The generator knows CI file formats, not your project's build steps, so the commands come from you, and no target's output carries a language or interpreter marker: the same selections produce the same file whatever language you build. There is no framework detection and no dependency resolution; plan to edit the output.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.