-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Capistrano 3.6.1 not deploying the latest revision if using a branch #2024
Comments
Is this possibly the same issue that you reported in #2023 under a different set of weirdness? |
No, @leehambley The issue there was that the repo_url changed and I have fixed it. Now I am seeing weird beahvior. The |
@leehambley Any idea why this is happening? Am I doing something wrong? I've just deployed |
From the output
looks largely correct, no? the I don't think that you can necessarily expect As a team we've been back and forward on that, but we use git-archive to checkout a named ref into a tar stream, which we stream back out into the newly created release dir, so I don't think that's a good indicator of whether the right thing was checked out or not. |
@jedrekdomanski can you clarify the problem a bit more? From your description it sounds like |
Yes, what @leehambley said 😃 The |
Thank you very much, for getting back to me, guys. I deployed another branch an hour ago and now I tried deploying my Here's the latest stacktrace just in case you wanted to compare...
|
@jedrekdomanski There is probably some underlying issue here because the deploy behavior should be consistent. However I am not sure there is much I personally can to do troubleshoot this from my side so I will leave it to you to keep an eye on the behavior and document your findings. I will keep this issue open for now. |
I've posted a similar issue several days ago but I am seeing weird behavior of Capistrano again when deploying different branch.
I want to test the deploymnet of my
maintenance
branch. I will use it whenever I want to turn off my application for the time of maitenance. I pushed the branch and this is my config.config/staging_maintenance.rb
The latest commit on this branch is
ae4980a47e0fdc8067d3d46683cf3464484b90eb
In
current
folder I check it:In the stacktrace I can see that
current
folder is symlinked with20190716095633
which is the latest release so I check it in20190716095633
folder.Everything fine.
But in
/repo
folder I do not see this commit:What's going on here?
This line confirms that the
maintenance
branch got deployed and the latest revision is atae4980a47e0fdc8067d3d46683cf3464484b90eb
I tried removing the
repo
folder and re-deploying but that didn't help. I shouldn't have to do that when I want to deploy a different branch, I think.Full stacktrace.
The text was updated successfully, but these errors were encountered: