Search
Blog posts
Introducing Git protections
Git protections add an extra layer of protection when deploying your code. They make sure the right resources get deployed to the right environments.Using Git resources directly in deployments
Additional support for sourcing dependencies directly from Git without intermediate packaging.Sourcing Kubernetes manifests from Git
You can now reference YAML configurations from your Git repository in the Deploy raw Kubernetes YAML step.Selenium series: populating the Git repo
In this post, we learn how to push our code to GitHub.How to structure your Git repository for DevOps automation
Learn how to structure your Git repositories to store your scripts, infrastructure as code configuration files, application configuration files, docs and more.Outage on octopus.com - report and learnings
Public incident report and our learnings about the octopus.com DNS disruption from January 25 – 26, 2023.Shaping Configuration as Code
We've been busy recently building Configuration as Code support for Octopus Deploy. Learn about some of the factors that shaped this feature.Expanding the use of execution containers
Octopus 2024.1 added the ability to use an inline Dockerfile or a URL to a Git repository to build the Docker container used for a deployment.Shaping Config as Code for variables
Learn how customer feedback informed updates to Configuration as Code.What is GitOps?
GitOps is an exciting new paradigm, but it can be hard to understand exactly what the term means.RFC: Version Control of Octopus configuration with Octopus Declarative
We want to build a great experience for people who want to store their Octopus configuration in Git.A first look at Tekton Pipelines
This blog explores Tekton Pipelines and discusses how they fit into the CI/CD ecosystemA first look at Jenkins X
Jenkins X is a complete mental shift from the traditional role of a CI server. In this post, we take a high-level look at Jenkins X and highlight why you need to appreciate it on its own terms.Running unit tests in Jenkins
As part of our series about Continuous Integration and build servers, learn how to run unit tests in Jenkins and capture the results.Octopus Deploy Config as Code: early access preview
Octopus Deploy's Configuration as Code solution is now available as a preview release for all customers.Fast track code promotion in your CI/CD pipeline
Learn how to use pre-approved deployment pipelines to rapidly promote code into productionUsing Jenkins Pipelines with Octopus
Learn how to trigger Octopus deployments with Jenkins PipelinesOctopus 2022 Q1: Config as Code for deployments
Octopus 2022 Q1: Config as Code for deployments is now available. Plus new integrations and an acquisition.Best practices for CI/CD
8 best practices for CI/CD, using agile, committing code frequently, using Config as Code, keeping builds green, automating your tests, using a feedback loop, and using fit for purpose technologies.
Loading...
Documentation
Migrating variables to Git
Variables needs to be manually migrated to Git for existing projectsConverting projects to Git
Converting a project to leverage the configuration as a code feature.octopus project convert
Convert a project to use Config As Codeoctopus project create
Create a projectCreating releases from a build server plugin on a version-controlled project
Examples of how to ensure that the right branch is used to create the release when using a build server plugin.Configuration as Code reference
Details about the configuration as code feature.Creating and deploying releases on a version-controlled project
What to expect when creating and deploying releases on a version-controlled project using the Configuration as Code feature in Octopus Deploy.octopus release create
Create a releaseConfiguration as Code
Projects can be version-controlled as text in a Git repositoryJenkins Pipeline projects
Managing Octopus steps in a Jenkins pipeline project.Runbook variables
How to use variables in runbooksCan't find what you are looking for? You can also search our support forum.