# Octopus CLI CI

Octopus CLI CI is a maintenance-only container image for the legacy Octopus CLI (octo), letting CI systems create releases, push packages, and manage Octopus Deploy deployments; the underlying CLI is archived and no. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/6306/octopus-cli-ci

## Description

Octopus CLI CI is a maintenance-only container image for the legacy Octopus CLI (octo), letting CI systems create releases, push packages, and manage Octopus Deploy deployments; the underlying CLI is archived and no longer under feature development.

## Platform availability

Available on 0 of 10 platforms.

## Health score

11/100 (Low), based on 3 of 4 factors.
- Maintained: 0 (GitHub repository is archived)
- Popular: 19 (8 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)

## Links

- GitHub: https://github.com/OctopusDeploy/OctopusCLI
- Docker Hub: https://hub.docker.com/r/octopuslabs/octopus-cli-ci
- Documentation: https://octopus.com/docs/octopus-rest-api/octopus-cli
- Official website: https://octopus.com/docs/octopus-rest-api/octopus-cli

## Common questions

### How can I authenticate the Octopus CLI in an automated CI environment?

The CLI needs to authenticate with the Octopus server. You can configure this using the octopus login command or by setting environment variables.

### How do I build and test the Octopus CLI locally?

Run ./build.sh on Unix-like systems or build.cmd on Windows. On Unix-like systems the build does not generate the OctopusTools NuGet package because that requires nuget.exe.

### Until when does the Octopus CLI receive security patches?

The Octopus CLI will continue to be supported for security patches until July 2023.

---
Source: Our Local Host (https://ourlocalhost.com/app/6306/octopus-cli-ci), the self-hosted and open-source app directory.
