# Install bitrise with Homebrew, Nix Command-line automation tool. Version 2.42.2 via Homebrew; verified 2026-07-30. Also installable with nix: nix profile install nixpkgs#bitrise. ## Install ```sh sudo av install brew:bitrise ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install bitrise ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#bitrise ``` Evidence: nixpkgs package indexes: pkgs/by-name/bi/bitrise/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:bitrise - **Package manager:** Homebrew - **Version:** 2.42.2 - **Source summary:** Command-line automation tool - **Homepage:** - **Repository:** - **Last updated:** 2026-07-30T18:22:00Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - bitrise (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 2.42.2 ## Project history and usage Bitrise CLI is the open source workflow runner behind Bitrise builds. The README describes it as the component that executes steps defined in bitrise.yml on Bitrise build machines and as a standalone tool for validating and running workflows locally. For package users, the CLI matters because it turns a hosted mobile CI product into a reproducible local command: brew install bitrise, run bitrise validate or bitrise run, and debug the same YAML-driven workflow before pushing. ### Project history The public repository was created in 2015 and has long used Go as a portable implementation language for local automation on macOS and Linux. Its tag history starts before 1.0 and continues through the v2 series, with v2.40.7 published in June 2026. Bitrise's own docs frame the CLI around bitrise.yml: users can download a project's configuration from bitrise.io or create a bitrise.yml in the project root, then run a named workflow locally. ### Adoption history Homebrew and Nix package entries in the input show adoption as a Unix developer tool rather than only a downloadable vendor binary. The README also points to Homebrew, Nix, GitHub releases, and community maintained packages. The CLI's adoption is tied to Bitrise's mobile CI ecosystem: it lets teams validate CI changes without waiting for a remote build and gives local access to the same workflow primitives used by hosted Bitrise. ### How it is used Common package-manager usage is to install the bitrise executable, keep bitrise.yml in the project root, run bitrise validate while editing the file, and run bitrise run workflow_name for local CI workflow execution. Secrets are intentionally split from the normal build config. Bitrise documents local secret handling with .bitrise.secrets.yml, which is package-nerd-important because it keeps the checked-in YAML portable while leaving local credentials outside the main workflow file. ### Why package nerds care Bitrise CLI is a good example of a hosted CI service exposing its runner as a packageable local binary. That makes the package more than a vendor helper: it is the executable contract for a CI configuration format. It also sits in the mobile-devops corner of package-manager culture, where macOS availability matters because iOS builds and signing workflows often start on developer Macs before being reproduced in CI. ### Timeline - 2015: bitrise-io/bitrise repository created. - 2016: Early 0.9.x and 1.x tags appear in the public tag history. - 2020s: README documents Homebrew and Nix installation paths alongside GitHub release downloads. - 2026: v2.40.7 release published on GitHub. ### Related projects - Bitrise CI is the hosted service whose builds are executed by the CLI runner. - bitrise-io/bitrise-steplib is the default step library source referenced by Bitrise configuration examples. - Bitrise workflow recipes and sample apps provide reusable examples around bitrise.yml workflows. ### Sources - - - - source_facts.package-manager ## Security Notes No matching local secret-handling manifest was found for bitrise. Nucleus package metadata is still published here so future coverage has a stable package URL. ## 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: bitrise.yml ## Credential files - Unix: .bitrise.secrets.yml ## Other Package-Manager Records - Nix - bitrise: normalized package name match | nixpkgs package indexes: pkgs/by-name/bi/bitrise/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/bitrise.yml](https://github.com/mxcl/pkgdb/blob/main/combined/bitrise.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph