You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When user issues a deploy command it would be great if Farmer would run a staging process before deploying on the already running production container so that we can have a fail-safe deployment on boxes.
So the deploy process would be as follows:
User runs farmer-cli deploy boxname1 -p tags/2.0 on a box currently on tags/0.1 pathspec.
Farmer clones boxname1 container completely as is in production.
Checks out tags/2.0 source code on cloned box.
Runs deploy script defined in .farmer.yml.
Runs status script defined in .farmer.yml and depending on status script exit code it determines if the deploy was successfully done with no errors.
If status script returned 0 exit code box will be updated to the new deployed container.
If status script returned a different exit code it leaves production box as is, and shows the error to the user.
aramalipoor
changed the title
[RFC] Staging new source code before running "deploy" command
Staging new source code before running "deploy" command
Sep 1, 2015
When user issues a deploy command it would be great if Farmer would run a staging process before deploying on the already running production container so that we can have a fail-safe deployment on boxes.
So the
deploy
process would be as follows:farmer-cli deploy boxname1 -p tags/2.0
on a box currently ontags/0.1
pathspec.boxname1
container completely as is in production.tags/2.0
source code on cloned box.deploy
script defined in .farmer.yml.status
script defined in .farmer.yml and depending on status script exit code it determines if the deploy was successfully done with no errors.Below is a sample
.farmer.yml
with status script:The text was updated successfully, but these errors were encountered: