Blocked Release Can Still be Deployed

Hi Octopus

When our automated tests fail we use the Octoposh module to block the release from our CI tool, the intention of this is to stop this version from being promoted or deployed elsewhere until the issues are resolved.

However a blocked release can still be deployed via both the command line and GUI (not tried the API). This seems like a bug unless I am mis-understanding the concept of blocking a release? My expectation is that this action should be prevented on a blocked release.

Can you confirm if this is a known issue that will be resolved? Its critical that we can mark releases as bad and prevent them from continuing in the lifecycle.



Thanks for reaching out. We already have a github issue submited for this one:

Sorry for the inconveniences. We’ll try to ship a fix for this one soon.