Have multiple release streams with our channels feature

Multiple channels of releases

Channels make it possible to have different streams of releases, with different steps, variables, lifecycles and code branches.

Try it free Channels guide

Multiple active streams of releases

Use channels to keep multiple streams of active releases - for example, a 1.x "stable" stream while you maintain what's in production today, and a 2.x "beta" stream while you work on the next big thing for tomorrow. Have different deployment steps, and build packages from different source code branches.

Learn more →

Keep multiple streams opens at once

Major vs. minor deployments

Sometimes a release might only have an incremental change, such as a CSS or code change, while other releases might require more drastic steps, like backing up the database and performing schema migrations. Use channels to define these different types of releases - 1.3 is a small release, but 1.4 requires a full deployment - and have different steps execute during the deployment.

Learn more →

Differentiate between major release streams and minor tweaks or adjustments

Hotfixes straight to production

Each project in Octopus has a lifecycle that can define rules like "you must deploy to test before you can deploy to production". Sometimes in an emergency you need to skip these phases, and go straight to production. Channels in Octopus can override the default lifecycle allowing certain releases to bypass these rules.

Learn more →

Users have the option with channels to override your default lifecycle to push a release straight to production, while avoiding other testing environments

Creating happy deployments at more than 25,000 companies, including:

Shout out to @OctopusDeploy for making their software so easy to work with. Just upgraded a 2 year out of date instance and migrated it to a new server and it worked with no effort beyond what their documentation said to do.

Twitter user Alex Dent Alex Dent
@DevOpsDent

We've been overhauling our internal infrastructure and back-end systems over the past month, including a move back to full @OctopusDeploy deployments; rediscovering how nice it is to have a platform-agnostic orchestrator that can deploy practically anything, anywhere ❤

Twitter user Nicholas Blumhardt Nicholas Blumhardt
@nblumhardt

Tools like @OctopusDeploy can be great in enabling culture change, we've been able to scale and improve our configuration story since we started using it https://buff.ly/2JyRmTY

Twitter user Niel Chalk Niel Chalk
@_neilch

Give your team a single place to release, deploy and operate your software.

Octopus Server

Octopus on your infrastructure.
Free for small teams, no time limits.

Download

Octopus Cloud

Octopus hosted by us.
Free 30-day trial.

Get started

Welcome! We use cookies and data about how you use our website allow us to improve the website and your experience, and resolve technical errors. Our website uses cookies and shares some of your data with third party analytics companies for these purposes.

If you decline, we will respect your privacy. A single cookie will be used in your browser to remember your preference.