As a pre-deploy step, require that the binaries in be uploaded to S3 before deploying the custom build.Add a large warning text when someone deploys a custom build to production (easy, but you still have to see the text in the output).There's several options to deal with this, with some options such as: Guarantee that the binaries are uploaded in the correct location in S3.I'm assuming that people will not remember (or know) to disable the admin setting flag for downloading from S3 ( EVG-13258) when deploying a custom build to production. Disable downloading binaries from S3 (so that it downloads from the app server).Because custom builds may or may not have uploaded the binaries to the S3 location, we have to come up with a way to do one of the following: In order for production to download from S3, the binaries must have been uploaded to the desired location in S3 or else binary downloads will fail. Staging will not download binaries from S3, but production will (to reduce load on the server during deploys).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |