Skip to content
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

Fail to deploy latest version #322

Closed
6 tasks done
onesvat opened this issue Feb 25, 2017 · 5 comments
Closed
6 tasks done

Fail to deploy latest version #322

onesvat opened this issue Feb 25, 2017 · 5 comments

Comments

@onesvat
Copy link

onesvat commented Feb 25, 2017

Before submitting your issue, please make sure that you've checked all of the checkboxes below.

  • You're running the latest release version of Deployer.
  • Ensure that you're running at least PHP 5.6.4, you can check this by running php -v
  • You've ran composer install --no-dev from the root of your installation.
  • You've ran npm install --production from the root of your installation.
  • You've ran rm -rf bootstrap/cache/* from the root of your installation.
  • You have restarted the queue listener and node socket server.

To help us better understand your issue, please answer the following.

Expected behaviour

The system should deploy latest available commit in the branch

Actual behaviour

The system re-deploys latest deployment, after second try it deploys new version.

Steps to reproduce

Deploy something, Commit something to repo, Wait some time, Deploy again, Deploy Again

Environment info

Operating System: 16.04
PHP Version: 7.0
Node Version: 4.7.3
Database System: MySQL
Database Version: 5.7

Logs (see storage/logs/) or other output that would be helpful

(If logs are large, please upload as attachment).

@lorvent
Copy link

lorvent commented Feb 25, 2017

do you mean,
with webhooks its failing
but when you deploy manually, its working?

@onesvat
Copy link
Author

onesvat commented Feb 25, 2017

Webhook failing too, I dont mention that. The problem is when i do manually deploy, I must do it twice time, because when the first try, it does not deploy latest version.

@REBELinBLUE
Copy link
Owner

Sounds like this is almost certainly the same issue as #323 I am just finishing up a fix right now

REBELinBLUE added a commit that referenced this issue Feb 25, 2017
…t should not be queued but done in sequence
@REBELinBLUE
Copy link
Owner

Can you change out branch bug/323 and see if that works?

@REBELinBLUE
Copy link
Owner

Moving discussing to #323

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants