OctopusDeploy
Automatic lifecycles deploys to environments where the release has never been
Severity
No response
Version
2023.3.12994
Latest Version
I could reproduce the problem in the latest build
What happened?
Automatic lifecycles consider environments where the release has never been; this causes a release to be deployed to an environment unexpectedly.
Reproduction
- Create environment Prod as the only environment in lifecycle Prod
- Create a project
- Create two tenants and connect them to the project and Prod
- Create a release (0.0.1) in the project and deploy it to all tenants in Prod
- Create an environment Test and a lifecycle Test (auto) -> Prod
- Connect one tenant to Test
- Create a release (0.0.2) in the project, which should automatically deploy to Test.
Note: 0.0.1 is in Prod for all tenants, 0.0.2 is in Test for Tenant 1 Deploy 0.0.1 to Prod again for the tenant that is not connected to Test Observe that 0.0.1 is auto-deployed to Test
Error and Stacktrace
No response
More Information
No response
Workaround
No response
The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future.
We prioritize issues based on the number of people affected, the impact type, and available workarounds.
If you’ve encountered this issue and haven’t informed our support team, please email [email protected]. Knowing how many people this issue affects helps us determine its priority.
