Reference
https://octopus.com/docs/getting-started
https://youtu.be/LPfi1IiIgzc?si=uz_KCEIMyLBfvIhT
Octopus Deploy
Deployment automation and release management tool
It is particularly useful in the context of CI/CD pipelines.
Features
- DevOps tool helps you automate your processes
- Release Management
- Deployment Automation
- Operations Runbooks
Octopus assumes you already have a CI system up and running, and we provide first-class integrations with all major CI systems on the market.
- CD platform: Octopus Deploy
- CI platforms:
- GitHub Actions
- GitLab
- Circle CI
- Jenkins
- JetBrains TeamCity
- BuildKite
- Azure DevOps
Hosting Octopus Deploy
(2 options)
- 🗄️ Self hosted → need to set Deployment target (https://octopus.com/docs/infrastructure/deployment-targets)
- ☁️Octopus Deploy Cloud
Projects, environments, and releases
Dashboard: (first landing page)
Projects: applications we deploy
Environments: where we deploy the applications. (i.e. Dev, Test, Production.)
Releases: bundle of all the things needed to deploy a specific version of an application.
Deployment process
Inside each project, you’ll configure a Deployment Process.
The deployment process is like the recipe for deploying the project
Example: [Deployment Process]
- Step 1: UI Deployment
- Step 2: API Deployment
- …etc
Variables
According to the environments, define your variables here
Infrastructure
Octopus Deploy organizes your deployment targets (the machines and services you deploy software to) into groups called environments.
💡 (i.e. Dev, Test, Production.)
Lifecycles
lifecycle 1: Dev → UAT → PROD
lifecycle 2: Dev → UAT → QA
lifecycle 3: DEV → QA
you can choose the lifecycle in project depend on your situation.Library-> Lifecycles
https://youtu.be/ofc-u61ukRA?si=QpJvkzJ0BOEtohJG
Tenants
When to use tenants?
- Need to deploy different versions of application to the same environment.
- Creating multiple environments of the same type. (multiple test environments for different testers, multiple production environments for different customers.)
- i.e.
- QA1 → QA1 team
- QA2 → QA2 team
- Japan region → Japan customer
- EU region → EU customer
- i.e.
