Lock and unlock releases

[antonmedv]

We really need to implement this feature.

• deploy:release
  Then new release dir created, LOCK file created within it.
  If prev release contains LOCK file, error throws.
• deploy:symlink
  After symlink LOCK file deleted.
• rollback
  Skip all release what contains LOCK file.
• cleanup
  Delete all release what contains LOCK file (check if current not linked to it).

[johnny-bit]

So... LOCK file is basically saying "we're in process of deploying here"? I quite get the concept for release, symlink & rollback (rolling to last complete release) however I don't get cleanup... If release acted like You said, then cleanup would have to be run twice - once befor release and once normally. maybe it would be better to add tasks like semaphores? acquire_lock and release_lock?

[gordalina]

👍

[antonmedv]

acquire_lock and release_lock - 👍

[Baldinof]

Is it necessary to have it on a per release basis ?

For my projects, I use these tasks, and it works good:

env('lock_path', '{{deploy_path}}/deploy.lock');

task('deploy:lock', function() {
    $res = run('[ -f {{lock_path}} ] && echo Locked || echo OK');

    if (trim($res) === "Locked") {
        throw new RuntimeException("Deployement is locked.");
    }

    run('touch {{lock_path}}');
});

task('deploy:unlock', function() {
    $res = run('[ -f {{lock_path}} ] && echo Locked || echo OK');

    if (trim($res) === "Locked") {
        run('rm {{lock_path}}');
    }
});

after('deploy:prepare', 'deploy:lock');
after('deploy:symlink', 'deploy:unlock');

[antonmedv]

Done in v4!