Level 75
Funny their site states zero downtime. I'd much rather do deployments the old-fashioned way and just be down a few minutes with a temporary page but know everything will be fine once everything is uploaded.
Dec 22, 2016
1
Level 4
New releases break existing file processes
Whenever a new release comes out on Envoyer, any existing process that is reading or writing a file can't complete. We get a ton of these sorts of errors:
[/home/forge/default/releases/20161222155437/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php > 171] (0) There is no existing directory at "/home/forge/default/releases/20161222155437/storage/accounts/3/logs/exports/users/20161222" and its not buildable: File exists
[/home/forge/default/releases/20161222155437/vendor/guzzlehttp/psr7/src/functions.php > 299] (0) Unable to open /home/forge/default/releases/20161222155437/storage/accounts/5/logs/data/users/20161222/process-20161222-175138.log using mode r: fopen(/home/forge/default/releases/20161222155437/storage/accounts/5/logs/data/users/20161222/process-20161222-175138.log): failed to open stream: No such file or directory
This is just a small example. Impacts jobs running across our system. The more frequent we push new deployments, the bigger a problem this sort of disruption has become.
Any ideas how to prevent this from happening in Envoyer?
Please or to participate in this conversation.