-
Notifications
You must be signed in to change notification settings - Fork 161
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
Pushing to Git from Travis fails: fatal: ref HEAD is not a symbolic ref #210
Comments
Is this sbt-release plugin issue? |
@xuwei-k Pushing to git otherwise works perfectly in builds that do not use |
Same here.
|
I am getting the same error while trying to use sbt-release in a Jenkins job. fatal: ref HEAD is not a symbolic ref |
Same error while running "release with-defaults" in travis-ci. I'm using sbt 0.13.15, sbt-release 1.0.6.
|
I have managed to fix this issue. |
@shklarsky @SrikanthTati @julianovidal I have this in Travis and I call it as part of the setup, and it seems to work. I don't pretend to understand the fine print just yet, or why this doesn't work inspite of you forcing non shallow git cloning, but there you go.
|
Hi all, we have the same problem in latest Jenkins, due to the way it gets sources from git repos. |
I tried the same solution as above and from this issue #60 but now I'm getting:
any ideas? |
Earlier I was getting this error, fatal: ref HEAD is not a symbolic ref . After proceeding as per the mentioned solutions, I am getting error as Any Idea about how to resolve this? |
Travis checks out the specific commit for some reason, rather than the branch name - so for example if you're using |
It would be great if this could be added as an option to the plugin, if it makes sense. (to force checkout of master) |
Have also tried:
Have tried all of the above, and yet to no avail.
Is there a way to do this properly? All the web trivia found is largely represented above but it doesn't seem to work.
The text was updated successfully, but these errors were encountered: