File deployed to production when it was not yet merged to master
Summary
Slack thread: https://gitlab.slack.com/archives/C101F3796/p1492828044572355
A blog post (gitlab-com/www-gitlab-com!5529 (merged)) was being worked on, and as of yet still in WIP and in its own branch. At some point, the blog post started to get deployed to production. You can see the file appear in this job, even though the file is not present in master branch yet. The file also does not exist in the last deploy to master's build artifacts, even though the subsequent deploy job shows it.
Perhaps there is an issue with the caching?
Build Job showing 4/22 post deployed:
Master repo showing it doesn't exist yet:
Last deploy to master's build artifact zip. Note that the deploy job did show the 4/22 file while the artifact file does NOT. Download Artifact File
Steps to reproduce
Unknown.
What is the current bug behavior?
File is erroneously deployed to production.
What is the expected correct behavior?
Only files in master branch are deployed.
Relevant logs and/or screenshots
See post is deployed to master even though MR is still not yet merged.