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

git tracking branch error #100

anandnalya opened this issue Feb 27, 2015 · 2 comments

git tracking branch error #100

anandnalya opened this issue Feb 27, 2015 · 2 comments


Copy link

@anandnalya anandnalya commented Feb 27, 2015


I'm trying to do a sbt-release from the master branch on jenkins but getting the following error:

[info] Starting release process off commit: 338bf143888957344045af2999a9bba38bac6e57
java.lang.RuntimeException: No tracking branch is set up. Either configure a remote tracking branch, or remove the pushChanges release part.

Following is the output of git remote show origin

showing remote tracking
Warning: Permanently added '[stash]:7999,[]:7999' (RSA) to the list of known hosts.
* remote origin
  Fetch URL: ssh://git@stash:7999/~analya/docker-test.git
  Push  URL: ssh://git@stash:7999/~analya/docker-test.git
  HEAD branch: master
  Local ref configured for 'git push':
    master pushes to master (up to date)

Am I missing something here?

Copy link

@anandnalya anandnalya commented Mar 3, 2015

For some reason, jenkins git was not setting the following properties which I had to do as a pre-built step

git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
git config branch.master.remote origin
git config branch.master.merge refs/heads/master

@anandnalya anandnalya closed this Mar 3, 2015
Copy link

@parayaluyanta parayaluyanta commented Jul 31, 2018

Based on sbt-release code -

if (!vcs(st).hasUpstream) {
--set-upstream followed by sbt release worked for me,

git push --set-upstream origin CURRENT_BRANCH_NAME
sbt release 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants