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

Newly pushed branches not being displayed for deployment #240

Closed
digster opened this issue Jul 1, 2016 · 6 comments
Closed

Newly pushed branches not being displayed for deployment #240

digster opened this issue Jul 1, 2016 · 6 comments

Comments

@digster
Copy link

digster commented Jul 1, 2016

While clicking on deploy, if the option to deploy the other branches is selected, any newly pushed branches after the last deployment are not displayed.
If any of the existing branch is then deployed, the git branch list gets updated and the new branches get available to deploy.
Ideally the git branch list should get periodically updated or an option should be given to explicitly do so.

@REBELinBLUE
Copy link
Owner

Do you have the cronjob running? It should update the list of available branches periodically

Stephen Ball
[email protected]

On 1 Jul 2016, at 10:59, digster [email protected] wrote:

While clicking on deploy, if the option to deploy the other branches is selected, any newly pushed branches after the last deployment are not displayed.
If any of the existing branch is then deployed, the git branch list gets updated and the new branches get available to deploy.
Ideally the git branch list should get periodically updated or an option should be given to explicitly do so.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@digster
Copy link
Author

digster commented Jul 1, 2016

Yes, the cronjob and supervisor tasks, both are running.

@criography
Copy link

criography commented Jul 1, 2016

I was actually about to ask you about this. I have no clue how much of a hassle would that be but something like a 'sync branches' button would be a nice fallback and a rather useful addition to the interface.
branch-sync

@REBELinBLUE
Copy link
Owner

REBELinBLUE commented Jul 3, 2016

Good idea @criography

@digster could you try running php artisan deployer:update-mirrors and tell if you that fixes the problem? If not, is there any output, and if not can you share the log from storage/logs/cli-YYYY-MM-DD.log

@digster
Copy link
Author

digster commented Jul 4, 2016

Turns out it was an issue with access permissions and fixing the same solved it. Although, the behavior of the cron script is unpredictable sometimes. Didn't seem to sync the deleted branches properly.
A dedicated sync button though sounds like a good idea.

@REBELinBLUE
Copy link
Owner

hmm, that is odd, it uses git clone --mirror to keep a copy of the remote repository. which should remove branches which have been deleted. Can you tell me which version of git is installed on your deployer server, git --version

Thanks

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