Shane Gill

icon company @OctopusDeploy

Results 15 comments of Shane Gill

Trigger may not fire if step set in release versioning doesn't match step set in channel

The issue arises when Octopus can not determine the version of an automatically created release. We consider this a configuration issue and will not issue a patch. When a project...

Improves unit test results stability across runs

Hi @fourpastmidnight, shipping your other 2 PRs as 3.6.5. This PR makes me the most nervous, not entirely convinced the changes are worth it considering how risk-averse we are for...

Deployment Overview doesn't consider "Channels" when Project is Tenanted and Overview page is filtered

Another report: https://octopus.zendesk.com/agent/tickets/149948

Don't delete unextracted package files as part of lifecycle retention

When do we want to remove the existing retention logic?

Multiple deployments transferring the same package takes up to a minute longer

We don't think this is an issue anymore. The mutex polls regularly to check if a package is still being acquired. Is anyone still encountering this problem?

Multiple deployments transferring the same package takes up to a minute longer

It is still happening: https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1661301347672109

Partially uploaded packages persist on the Octopus Server

Customer report where temporary files filled up the OS disk: https://octopusdeploy.slack.com/archives/C03KW5024M9/p1666893446172759

Partially uploaded packages persist on the Octopus Server

As part of this issue, consider that it is surprising anything is being persisted to a location other than the configured Octopus home directory.

Upgrading tentacles in a specific environment blocks deployments / runbook runs for all environments

Similar issue: https://github.com/OctopusDeploy/Issues/issues/3535

Package Retention Policies on Runbooks are hardcoded to 90 days

An issue has been addressed to reduce the deployment journal size: https://github.com/OctopusDeploy/Issues/issues/8310