Getting started
From an empty repository to a green build in about five minutes.
Requirements
Section titled “Requirements”- An account in an organisation on a Vulcan CI instance.
gitand a repository you can push to.- Linux or macOS on the machine running the CLI. Workers are provisioned by your platform admins — nothing to install for builds.
Install the CLI
Section titled “Install the CLI”$ curl -sSf https://get.vulcan-ci.io | shVerify the install:
$ vulcan --versionvulcan 0.1.0Authorise the CLI
Section titled “Authorise the CLI”$ vulcan auth login --instance https://vulcan.example.comThis opens Forge in your browser. Sign in, approve the request, and the CLI stores a scoped API token in ~/.config/vulcan/credentials. Tokens can be reviewed and revoked at any time under Profile → My API tokens.
Register a project
Section titled “Register a project”From the root of your repository:
$ vulcan initCreated .vulcan/workflows/ci.yaml$ vulcan project registerRegistered project payments-api in organisation acmevulcan init writes a starter workflow; Workflow config covers every key. Commit the .vulcan/ directory — workflow definitions are versioned with your code.
Trigger your first build
Section titled “Trigger your first build”Builds start on push by default. To trigger one by hand and follow it:
$ vulcan build trigger --workflow ciBuild #1 queued on pool default$ vulcan build watchci / verify / unit … running 00:41Open the build in Forge to see the workflow graph, per-step logs, and timing. The project page keeps a history strip of recent builds.
Next steps
Section titled “Next steps”- Workflows — how phases, steps, and dependencies fit together.
- Workflow config — the full YAML schema.
- CLI reference — every command and flag.