Install go-agent with Homebrew Cask

Project links

• Homepage

Commands and aliases

• go-agent

Project history

GoCD's own project-status history traces the product back to Cruise, first released by ThoughtWorks in 2007. The product was renamed Go in 2010, gained a community edition in 2011, and was open-sourced in 2014 as GoCD. After that shift, the server, agent, plugins, and documentation were maintained as an open source continuous-delivery platform.

The agent package reflects GoCD's architecture: servers store pipelines and schedule work, while agents run tasks, report status, and advertise resources. Documentation for installation and auto-registration shows the agent as a configurable service with properties files and a registration workflow rather than a developer-only command.

Adoption history

GoCD gained adoption among teams that wanted modeled deployment pipelines, visual pipeline history, and agent-based execution instead of a single-node build tool. The agent model let teams add capacity by attaching more machines with selected resources and environments.

The macOS cask matters because some pipelines need Apple hardware, macOS-specific tests, signing steps, or packaging work. A packaged agent lowers the friction of turning such a host into part of a GoCD installation.

How it is used

Practitioners install the agent, point it at a GoCD server, and register it manually or through auto-registration properties. Once accepted by the server, the agent runs jobs from pipelines, uses configured resources to match job requirements, and stores local service configuration under its installation and state directories.

Administrators use the cask package as one deployment path for a long-running agent service. The important operational files are wrapper properties and autoregistration properties, especially where a registration key or agent resources are managed by automation.

Why package nerds care

GoCD Agent is a cask-flavored CI worker rather than a typical desktop app. It packages a service process, Java-based delivery tooling, and registration state, which makes it a useful example of Homebrew Cask carrying infrastructure software.

Timeline

• 2007: ThoughtWorks released Cruise, the product that became GoCD.
• 2010: Cruise was renamed Go.
• 2011: A community edition was released.
• 2014: GoCD was open-sourced.
• 2020: Previously paid features were made open source under the GoCD project.

Related projects

• GoCD Server schedules pipelines and coordinates agents.
• GoCD plugins extend source-control, artifact, elastic-agent, notification, and task behavior.
• Agent auto-registration connects installation automation to GoCD server administration.

Sources

• https://docs.gocd.org/current/advanced_usage/agent_auto_register.html
• https://docs.gocd.org/current/installation/install/agent/osx.html
• https://github.com/gocd/gocd
• https://www.gocd.org/2023/02/13/gocd-project-status