# Install gitlab-ci-local with Homebrew, Nix Run gitlab pipelines locally as shell executor or docker executor. Version 4.73.0 via Homebrew; verified 2026-06-23. ## Install ```sh sudo av install brew:gitlab-ci-local ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install gitlab-ci-local ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#gitlab-ci-local ``` Evidence: nixpkgs package indexes: pkgs/by-name/gi/gitlab-ci-local/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:gitlab-ci-local - **Package manager:** Homebrew - **Package manager page:** - **Version:** 4.73.0 - **Source summary:** Run gitlab pipelines locally as shell executor or docker executor - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MIT - **Source archive:** - **Last updated:** 2026-06-23T12:38:37Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - gitlab-ci-local (cli) - gitlab-ci-local (alias) ## Dependencies - node ## Install behavior - Post-install hook: not defined - Bottle: available on all ## Freshness - Page generated: 2026-07-08 - Package-manager version: 4.73.0 - Package-manager updated: 2026-06-23 - Local data: ok - Upstream repository: https://github.com/firecow/gitlab-ci-local - info: No cached GitHub release or tag data was available. ## Project history and usage gitlab-ci-local is a command-line runner for executing GitLab CI pipelines on a developer machine with shell or Docker executors. It is built around the recurring developer problem described by its README: avoiding repeated pushes just to discover whether `.gitlab-ci.yml` behaves as expected. ### Project history The GitHub repository was created in January 2020. The README positions the tool as a replacement for project-specific shell scripts and make targets by letting developers run the same GitLab CI jobs locally. The project expanded beyond a basic runner into a package with Debian repository instructions, AUR packaging, npm and Bun installation, Homebrew installation, Windows Git Bash support, dotenv-style defaults, tab completion, job listing modes, and documented behavior for includes, artifacts, variables, and local-only jobs. ### Adoption history gitlab-ci-local's adoption follows the spread of GitLab CI into projects that wanted faster feedback than remote pipeline runs. Repository metadata collected for this enrichment reported 3,978 GitHub stars, and the package is distributed through npm, Homebrew, distro-oriented channels, and Arch's AUR. Its ecosystem significance comes from matching GitLab CI's YAML-centered workflow while accepting that a local runner has boundaries. The README documents tracked-file behavior, local-only rules, variables from home and project files, remote variables, and artifact handling so teams can decide what belongs in local feedback and what belongs in GitLab. ### How it is used Practitioners install the CLI, run `gitlab-ci-local` in a repository, use `.gitlab-ci-local-env` or `$HOME/.gitlab-ci-local/.env` for default CLI options, and use variables files to model CI/CD variables. They also use `--list`, `--list-all`, and CSV listing modes to inspect planned jobs before executing a pipeline. ### Why package nerds care For package nerds, gitlab-ci-local is interesting because it turns a hosted CI product's YAML dialect into a local executable distributed through several package ecosystems. It is the sort of package that saves time in inner-loop development while surfacing the hard parts of reproducing CI outside the hosted service. ### Timeline - 2020: Repository created for local GitLab CI execution. - 2020: README described running GitLab pipelines locally as shell or Docker executor. - 2024: npm package metadata exposed the `gitlab-ci-local` binary entry point. - 2026: v4.73.0 release published on GitHub. ### Related projects - Related surfaces include GitLab CI, Docker, shell executors, npm, Bun, Homebrew, Debian packaging, AUR, and Git Bash on Windows. ### Sources - - - - - - ## Security Notes generalized runtime or code generation signal. - **Geiger risk:** yellow / medium - generalized runtime or code generation signal ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: .gitlab-ci.yml, .gitlab-ci-local-env, ~/.gitlab-ci-local/.env ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** gitlab-ci-local - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Nix - gitlab-ci-local: normalized package name match | nixpkgs package indexes: pkgs/by-name/gi/gitlab-ci-local/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Related links - [Cloud CLI packages](https://www.automicvault.com/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family. - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [node](https://www.automicvault.com/pkg/brew/node/) - Runtime dependency declared by Homebrew. - [gitlab-ci-linter](https://www.automicvault.com/pkg/brew/gitlab-ci-linter/) - Shares av.db curated category or tags: ci, ci-cd, cli, developer-tools, gitlab. - [gitlab-runner](https://www.automicvault.com/pkg/brew/gitlab-runner/) - Shares av.db curated category or tags: ci, ci-cd, cli, developer-tools, gitlab. - [act](https://www.automicvault.com/pkg/brew/act/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools, docker. - [actionlint](https://www.automicvault.com/pkg/brew/actionlint/) - Shares av.db curated category or tags: ci, ci-cd, cli, developer-tools. - [actions-up](https://www.automicvault.com/pkg/brew/actions-up/) - Shares av.db curated category or tags: ci, ci-cd, cli, developer-tools. - [codecov-cli](https://www.automicvault.com/pkg/brew/codecov-cli/) - Shares av.db curated category or tags: ci, ci-cd, cli, developer-tools. - [brigade-cli](https://www.automicvault.com/pkg/brew/brigade-cli/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools. - [circleci](https://www.automicvault.com/pkg/brew/circleci/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools. - [gitlab-ci-local](https://www.automicvault.com/pkg/npm/gitlab-ci-local/) - Same normalized package name appears in another local ecosystem. Shared terms: ci, gitlab, gitlab-ci-local, local, pipeline. - [pipelight](https://www.automicvault.com/pkg/brew/pipelight/) - Local package facts share a topical domain. Shared terms: ci, ci-cd, cli, developer, developer-tools. - [gitlab-ci-local](https://www.automicvault.com/pkg/npm/gitlab-ci-local/) - Same normalized package name in another local ecosystem. ## Combined YAML source View the package source record on GitHub. [combined/gitlab-ci-local.yml](https://github.com/automic-vault/db/blob/main/combined/gitlab-ci-local.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph