Michael Grosser

- these 'random' deploys are for the canary stage ? - these 'random' deploys are duplicates (deploying the same sha/branch as another deploy) ? I'd guess there is a webhook...

Try turning off the `Automatically deploy new releases`

if that solves it then we just need some new logic in the integration controller to never do duplicate deplosy

Did you set up a deploy pipeline between canary and production ? ... or are you manually doing that ? If there is nothing connecting the 2 stages and no...

hmm weird ... so buildkite triggers a release ... which should trigger a deploy to canary and then production ... that sounds about right :/ how about add a webhook...

Nope, that's about it On Tue, Aug 8, 2017 at 10:38 PM, Jacob Bednarz wrote: > I've swapped to using the webhook for the stage and turned off automatic >...

maybe put a `Rails.logger.error("DEPLOY START" + caller.join("\n"))` into the DeployService so it logs where these deploys are coming from ... the check the logs when it happens again

locks are only kept in-memory ... so should be cleared after restart :(

yeah that message is wrong ... should not say that when it's not in the queue ... might hint at some bug where the deploy is either created by a...

maybe at the time of he check the CI run was still pending ? ... still there on refresh ? ... dig into that more, maybe a issue in commit_status.rb