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

Add git version requirements #1532

Closed
grahl opened this Issue May 26, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@grahl
Copy link
Contributor

grahl commented May 26, 2017

My system information:

  • Operating system type: CentOS
  • Operating system version: 7.x
  • BLT version: 8.8.3

When I run this command:

vendor/bin/blt deploy -Ddeploy.branch="master-build" -Ddeploy.commitMsg="My message"

I get the following output:

blt > deploy:push-remote:
     [exec] To git@MYREPO.git
     [exec]  ! [rejected]        master-build -> master-build (non-fast-forward)
     [exec] error: failed to push some refs to 'git@ MYREPO.git
     [exec] hint: Updates were rejected because the tip of your current branch is behind
     [exec] hint: its remote counterpart. Merge the remote changes (e.g. 'git pull')
     [exec] hint: before pushing again.
     [exec] hint: See the 'Note about fast-forwards' in 'git push --help' for details.

The problem is the git version available on stock CentOS (1.8.x), which handles force pushing differently. Locally I had 2.11 working via homebrew.

I've resorted to building a second copy of git from source for blt due to other conflicting dependencies
in my setup.

Could you please either add an environment check that git is too old to deploy successfully or adjust your system requirements documentation to highlight this?

grasmash added a commit to grasmash/bolt that referenced this issue May 31, 2017

@grasmash grasmash self-assigned this May 31, 2017

@grasmash grasmash closed this in ecc0666 May 31, 2017

@grasmash grasmash removed the in progress label May 31, 2017

@grahl

This comment has been minimized.

Copy link
Contributor Author

grahl commented Jun 2, 2017

Awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.