Hi Octopus Support,
We’ve just encountered something which looks like a critical bug.
We have a project which was deployed to the STAGE environment:
- Release 220.127.116.116 was deployed to 4 web nodes on August 1 (it was one deployment to all 4 nodes)
- Release 18.104.22.1682 was deployed to 4 web nodes on August 2 (it were 2 deployments: one to nodes 1&3, another to nodes 2&4)
The project has an Auto-Deploy trigger set to fire on event group “Machine becomes available for deployment”.
On August 4, the trigger fired and deployed the old version - 22.214.171.1246 - to all 4 web nodes.
Please investigate this urgently, this is a huge showstopper. We are now disabling all the triggers in all our projects.
This is cloud instance connect.octopus.app.
- Release 126.96.36.1996
- Release 188.8.131.522
- Auto-Deploy of Release 184.108.40.2066