Generic CI

If you’re not on GitHub Actions, you can integrate no-tickets with three lines of shell. The CLI handles validation, delta computation, and the push itself; your CI only needs to install it and run nt push. This guide works for GitLab CI, CircleCI, Jenkins, Buildkite, Drone, Bitbucket Pipelines, or anything else that runs Linux/macOS shells with internet egress.

Prerequisites

A no-tickets project — create one in the dashboard.
A push token from Project settings → Tokens.
The token stored as a CI secret called NT_PUSH_TOKEN.

The three-line snippet

curl -fsSL https://get.no-tickets.com | sh         # install the CLI
export NT_PUSH_TOKEN="$NT_PUSH_TOKEN"               # already in env via CI secret
nt push --ci                                        # send the delta

--ci tells the CLI to mark the push as origin: ci and to pull commit SHA / branch / PR number / build URL from the CI environment automatically (GitLab, CircleCI, Jenkins, Buildkite, and Drone variables are all detected). On unknown systems, set the metadata explicitly:

nt push --ci \
  --commit "$CI_COMMIT_SHA" \
  --branch "$CI_BRANCH" \
  --build-url "$CI_BUILD_URL"

Per-system examples

GitLab CI

# .gitlab-ci.yml
notickets:
  stage: deploy
  image: alpine:latest
  variables:
    NT_PUSH_TOKEN: $NT_PUSH_TOKEN
  before_script:
    - apk add --no-cache curl bash
    - curl -fsSL https://get.no-tickets.com | sh
  script:
    - nt push --ci
  rules:
    - if: '$CI_COMMIT_BRANCH == "main"'
    - if: '$CI_PIPELINE_SOURCE == "merge_request_event"'

CircleCI

# .circleci/config.yml
version: 2.1

jobs:
  notickets-push:
    docker:
      - image: cimg/base:current
    steps:
      - checkout
      - run:
          name: Install nt
          command: curl -fsSL https://get.no-tickets.com | sh
      - run:
          name: Push
          command: nt push --ci

workflows:
  notickets:
    jobs:
      - notickets-push:
          context: notickets   # holds NT_PUSH_TOKEN

Jenkins (Pipeline)

pipeline {
  agent any
  environment {
    NT_PUSH_TOKEN = credentials('notickets-push-token')
  }
  stages {
    stage('no-tickets push') {
      steps {
        sh 'curl -fsSL https://get.no-tickets.com | sh'
        sh 'nt push --ci'
      }
    }
  }
}

Buildkite

# .buildkite/pipeline.yml
steps:
  - label: ":notebook: no-tickets push"
    command: |
      curl -fsSL https://get.no-tickets.com | sh
      nt push --ci
    env:
      NT_PUSH_TOKEN: ${NT_PUSH_TOKEN}

Caching the CLI install

The install script is a single static binary, so it’s small (~6 MB). On systems with build caches you can speed up CI by caching ~/.local/bin/nt between runs:

# CircleCI example
- restore_cache:
    keys: [nt-binary-{{ .Environment.NT_CLI_VERSION }}]
- run: test -x ~/.local/bin/nt || curl -fsSL https://get.no-tickets.com | sh
- save_cache:
    key: nt-binary-{{ .Environment.NT_CLI_VERSION }}
    paths: [~/.local/bin/nt]

Pin NT_CLI_VERSION so cache busts when you bump the CLI.

Exit codes

Code	Meaning	Recommended CI behaviour
`0`	Push succeeded	continue
`1`	Validation failed (malformed frontmatter, invalid task syntax)	fail the build
`2`	Network / auth failure	retry once, then fail
`3`	Entitlement exceeded (hard cap — projects, tokens, agent seats)	fail the build

Soft-cap breaches (push volume) never return a non-zero exit code; the team owner gets an email at 80% and 100% of monthly volume and pushes keep going through. See Entitlements for the full soft/hard split.

Getting Started

Markdown Format

Concepts

Integration Guides

Troubleshooting

FAQ

Prerequisites

The three-line snippet

Per-system examples

GitLab CI

CircleCI

Jenkins (Pipeline)

Buildkite

Caching the CLI install

Exit codes

See also

​Prerequisites

​The three-line snippet

​Per-system examples

​GitLab CI

​CircleCI

​Jenkins (Pipeline)

​Buildkite

​Caching the CLI install

​Exit codes

​See also

Prerequisites

The three-line snippet

Per-system examples

GitLab CI

CircleCI

Jenkins (Pipeline)

Buildkite

Caching the CLI install

Exit codes

See also