# Install travis with Homebrew, apt Command-line client for Travis CI. Version 1.14.0 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:travis ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install travis ``` Evidence: local Homebrew formula metadata ### Linux - Debian apt (92%): ```sh sudo apt install travis ``` Evidence: Debian stable package indexes: travis from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz ## Package facts - **Package key:** brew:travis - **Package manager:** Homebrew - **Package manager page:** - **Version:** 1.14.0 - **Source summary:** Command-line client for Travis CI - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MIT - **Source archive:** - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - travis (cli) - travis (alias) ## Dependencies - ruby@3.4 ## Build dependencies - pkgconf ## Uses from macOS - libffi ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 1.14.0 - Local data: ok - Upstream repository: https://github.com/travis-ci/travis.rb - Upstream latest detected: v1.14.0 (current) - info: No package-manager update timestamp was available. ## Project history and usage The Travis CI Client is the Ruby `travis` gem and command-line client for interacting with Travis CI services. The official README describes it as both a CLI and Ruby library that can talk to travis-ci.com or a custom Travis CI setup using a GitHub account. ### Project history The client belongs to the era when Travis CI became a default continuous-integration service for GitHub-hosted open-source projects. Its README is structured around a large CLI command set, a Ruby client library, installation instructions, troubleshooting, and version history, reflecting its dual role as both user tool and programmable Travis API wrapper. The CLI's command surface tracks the lifecycle of Travis CI usage from local setup to build operations: logging in, choosing API endpoints, enabling or disabling repositories, validating `.travis.yml`, encrypting secrets, managing environment variables and SSH keys, viewing build history, streaming logs, restarting jobs, and opening builds in a browser. The README also documents the transition from travis-ci.org and travis-ci.com endpoint shortcuts to the current API endpoint model, plus support for Travis CI Enterprise or custom deployments. That makes the package a historical marker for the hosted-CI and GitHub integration period of developer tooling. ### Adoption history Adoption followed Travis CI's GitHub-centered workflow. Developers installed the gem or package, authenticated with GitHub-backed Travis accounts, and used the `travis` executable to initialize projects, lint `.travis.yml`, enable repositories, inspect builds, and manage encrypted configuration without leaving the terminal. The batch input records Homebrew, Debian, and Ubuntu packaging, showing that the client was not only a RubyGems artifact but also a system package for users who expected CI tools to be installable from their operating-system package manager. ### How it is used Common package-nerd usage centers on repository automation: `travis init` creates CI configuration, `travis lint` validates `.travis.yml`, `travis encrypt` and `travis encrypt-file` help place secrets in build configs, `travis logs` streams test logs, and `travis status`, `show`, `history`, `restart`, and `cancel` operate on builds and jobs. Authentication and endpoint management are also part of the tool's identity. The README documents `travis login`, token handling, endpoint selection for travis-ci.com or travis-ci.org, and an interactive console for inspecting Travis API entities from Ruby. ### Why package nerds care For package-manager users, the Travis CLI represents the period when CI configuration became a dotfile-and-terminal workflow. It let maintainers bootstrap `.travis.yml`, encrypt secrets, and debug remote CI jobs from a local shell, making CI feel like another command-line development tool. Its history matters because it sits at the intersection of RubyGems, Homebrew, Debian/Ubuntu packages, GitHub OAuth, and hosted CI APIs. The package is less a single-purpose binary than a compact interface to the operational culture around Travis CI. ### Timeline - 2010s: Travis CI client develops as a Ruby gem with both CLI and Ruby library interfaces. - 2010s: README documents travis-ci.org, travis-ci.com, and Enterprise endpoint support. - 2020s: README and docs continue to point users at travis-ci.com and API-backed CLI workflows. ### Related projects - Related to Travis CI's hosted service and API documentation. - Comparable in role to other CI provider CLIs that manage repository setup, build status, logs, secrets, and deploy settings. - Closely tied to `.travis.yml`, the repository-local Travis CI build configuration file. ### Sources - Batch input fields: current_curation.config-file-location, current_curation.credentials-file-location, source_facts.package-manager - Official README: https://github.com/travis-ci/travis.rb#readme - Official Travis CI documentation: https://docs.travis-ci.com/ ## Security Notes broad file, network, media, or database tool signal. - **Geiger risk:** blue / medium - broad file, network, media, or database tool 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: ~/.travis/config.yml ## Credential files - Unix: ~/.travis/config.yml ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** travis - **Version Scheme:** 0 - **Revision:** 2 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Debian apt - travis - 220729-1: normalized package name match | Debian stable package indexes: travis from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | trajectory analyzer and visualizer | http://www.travis-analyzer.de - Ubuntu apt - travis - 220729-1: normalized package name match | Ubuntu 24.04 LTS package indexes: travis from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | trajectory analyzer and visualizer | http://www.travis-analyzer.de ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Package publisher tools](https://www.automicvault.com/pkg/package-publishers/) - Belongs to a package publishing or registry 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. - [ruby@3.4](https://www.automicvault.com/pkg/brew/ruby-3-4/) - Runtime dependency declared by Homebrew. - [pkgconf](https://www.automicvault.com/pkg/brew/pkgconf/) - Build dependency declared by Homebrew. - [litani](https://www.automicvault.com/pkg/brew/litani/) - Shares av.db curated category or tags: ci, cli, developer-tools. - [pinact](https://www.automicvault.com/pkg/brew/pinact/) - Shares av.db curated category or tags: ci, cli, developer-tools. - [wrkflw](https://www.automicvault.com/pkg/brew/wrkflw/) - Shares av.db curated category or tags: ci, cli, developer-tools. - [act](https://www.automicvault.com/pkg/brew/act/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools. - [anycable-go](https://www.automicvault.com/pkg/brew/anycable-go/) - Shares av.db curated category or tags: cli, developer-tools, ruby. - [bitrise](https://www.automicvault.com/pkg/brew/bitrise/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools. - [brew-gem](https://www.automicvault.com/pkg/brew/brew-gem/) - Shares av.db curated category or tags: cli, developer-tools, ruby. - [brigade-cli](https://www.automicvault.com/pkg/brew/brigade-cli/) - Shares av.db curated category or tags: ci-cd, cli, developer-tools. - [cargo-hack](https://www.automicvault.com/pkg/brew/cargo-hack/) - Local package facts share a topical domain. Shared terms: cli, continuous, continuous-integration, developer, developer-tools. - [ghi](https://www.automicvault.com/pkg/brew/ghi/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, command-line, developer, developer-tools, line. ## Combined YAML source View the package source record on GitHub. [combined/travis.yml](https://github.com/automic-vault/db/blob/main/combined/travis.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