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

Deploy: Remove obsoleted git remote checking #999

Merged
merged 1 commit into from
Aug 9, 2018

Conversation

tangrufus
Copy link
Collaborator

Remove obsoleted git remote checking tasks introduced in #299 because recent Ansible versions are able to detect/handle git remote changes.

See: https://discourse.roots.io/t/do-we-still-need-git-remote-checking-during-deploy/12639

@swalkinshaw
Copy link
Member

Were you able to verify the behaviour? Or should we try and do that first?

- name: Clone project files
git:
repo: "{{ project_git_repo }}"
dest: "{{ project_source_path }}"
version: "{{ project_version }}"
accept_hostkey: "{{ project.repo_accept_hostkey | default(repo_accept_hostkey | default(true)) }}"
force: yes
Copy link
Collaborator Author

@tangrufus tangrufus Jul 2, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Side Effect

Before this pull request:
If /srv/www/XXXX/shared/source being modified, deploy will fail. And, no useful message printed because of no_log: true. Instead, a misleading Git repo {{ project.repo }} cannot be accessed will be printed on the next task.

After this pull request:
If /srv/www/XXXX/shared/source being modified, the changes will be discarded during deploy because of force: yes.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's better anyway 👍

Remove obsoleted `git` remote checking tasks introduced in roots#299
because recent Ansible versions are able to detect/handle `git` remote
changes.

See: https://discourse.roots.io/t/do-we-still-need-git-remote-checking-during-deploy/12639
@partounian
Copy link
Contributor

Seems like a good thing to merge

@tangrufus
Copy link
Collaborator Author

Tests changing between 2 repos(one with subtree and one without) back and forth. It looks good to me.

Did anyone find any bugs?

@swalkinshaw
Copy link
Member

Perfect, thank you 👍

@swalkinshaw swalkinshaw merged commit bf22d2d into roots:master Aug 9, 2018
@tangrufus tangrufus deleted the deploy-git branch August 9, 2018 03:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants