-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid unnecessary releases #1755
Comments
Nice idea |
Howdy! In versoin 6.4.7, this new "feature" will break deployment, if you don't have set any This could be possible if you're doing e.G. a deploy via CI by running composer + rsync to push the code to server. This command should only run if Commit is here: bb4d41c#diff-47a8209fdc160285dc659ed27fba1861 |
@Chrico You just need to set the # your ci deploy file.
set('check_remote_head', false) |
The problem is this line: https://github.com/deployphp/deployer/blob/v6.4.7/recipe/deploy/prepare.php#L45 which runs even if the Additonally it could be possible, that the server has no access to the repo itself. So you should probably use |
@Chrico You are right, I'll look into that. Thanks. |
I dot this. :) See 85aae9f |
Usage: require 'recipe/deploy/check_remote.php';
after('deploy:prepare', 'deploy:check_remote'); |
|
Description
Each time I run
dep deploy ...
, the deployer will immediately work, and this is how it suppose to be, but sometimes I don't have any changes in my code, and if I rundep deploy ...
a new unnecessary release will be created.For example:
I use
at
command to run deployer every day at midnight:Deployer has to skip the deployment if no changes were made into the git repo.
Solution
Whenever deployer finishes, a new file contains the last commit id will be created/updated in
.dep
folder.The next time we deploy, deployer has to check if the current commit id matches the existing saved one, if so then it will skip the deployment.
I will work on this if accepted.
The text was updated successfully, but these errors were encountered: