error in git push

[gerhard]

error in git push

[gerhard]

I must say, I am quiet surprised that this didn't work. Do you have git installed on the remote host?

While deliver is completely configurable, the default strategies rely on git.

Could you paste the entire deliver log? Deliver logs everything to /tmp/deliver-[app-name] ; ).

echo -n > /tmp/deliver-[app-name] # clear the file
deliver --verbose # re-deliver the app
cat /tmp/deliver-[app-name] | pbcopy # let's see the log then!

[videoMonkey]

The log as requested:

Mon  9 Jul 2012 13:50:19 CEST ::: �[1m�[32mDELIVERING [app-name] WITH NODEJS STRATEGY�[0;10m
Mon  9 Jul 2012 13:50:19 CEST ::: �[33m----->�[0;10m �[1m�[37mEnsuring remote is ready to accept git pushes�[0;10m
Mon  9 Jul 2012 13:50:19 CEST ::: [app-name]@nodejs01-[app-name] : 
    set -e
    if [ ! -d ~[app-name]/app ]
    then
      mkdir ~[app-name]/app
      cd ~[app-name]/app
      git init 
      git config receive.denyCurrentBranch ignore
    fi

Mon  9 Jul 2012 13:50:20 CEST ::: �[33m----->�[0;10m �[1m�[37mPushing new commits with git to: [app-name]@nodejs01-[app-name]�[0;10m
Mon  9 Jul 2012 13:50:20 CEST ::: JOB: git push -f [app-name]@nodejs01-[app-name] node 

And this was the terminal output:

Counting objects: 5, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 375 bytes, done.
Total 4 (delta 1), reused 0 (delta 0)
remote: error: refusing to update checked out branch: refs/heads/node
remote: error: By default, updating the current branch in a non-bare repository
remote: error: is denied, because it will make the index and work tree inconsistent
remote: error: with what you pushed, and will require 'git reset --hard' to match
remote: error: the work tree to HEAD.
remote: error: 
remote: error: You can set 'receive.denyCurrentBranch' configuration variable to
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing into
remote: error: its current branch; however, this is not recommended unless you
remote: error: arranged to update its work tree to match what you pushed in some
remote: error: other way.
remote: error: 
remote: error: To squelch this message and still keep the default behaviour, set
remote: error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.
To [app-name]@nodejs01-[app-name]:~[app-name]/app
 ! [remote rejected] node -> node (branch is currently checked out)
error: failed to push some refs to '[app-name]@nodejs01-[app-name]:~[app-name]/app'

FAILED  1:
git push -f [app-name]@nodejs01-[app-name] node 

I was looking at your code and it seems that the adjusting of the setting in git to recieve is not happening. If I ssh into the server and do a git pull before running the command everything happens just fine. It's only when I have changes to run that things go wrong.

For my part, don't worry about this too much, I have the code running on what will be the production server and I really need to get back to site/app code. I want to revisit deployment later this month.

[gerhard]

There's something different about your setup. I have a feeling the git config receive.denyCurrentBranch ignore command doesn't get to run (and potentially the git init before). Maybe a permissions issue?

This will sound a bit hack-ish, but try changing the set -e to set -x in the deliver/libexec/common file, init_app_remotely() function. Now run deliver in verbose mode (-V or --verbose flag). This ought to flush out the specific failure.

Just pushed a nodejs app for the first time, to a local VM. That's using a slightly customised nodejs strategy, but nothing special.

[videoMonkey]

Well, today is live day, and I am working from a different development station but with all the same code and things seem to be working. I am going to close the issue.

[gerhard]

Glad to hear things are working!

Would be interesting to find out what exactly was going wrong (for future reference). It's not important though, happy to leave it at this. Cheers!

[bijanv]

This happened for me as well, had to do a git push on that branch on the remote server and then try deliver again and it worked.