[chef] Re: Re: Re: Re: Re: Issue deploying with application cookbook - STDERR: fatal: reference is not a tree: af5c7ff84dd852cf1c0b5ca60ea92546a20dda01


Chronological Thread 
  • From: Daniel DeLeo < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Issue deploying with application cookbook - STDERR: fatal: reference is not a tree: af5c7ff84dd852cf1c0b5ca60ea92546a20dda01
  • Date: Tue, 23 Jul 2013 18:07:29 -0700

On Tuesday, July 23, 2013 at 2:05 PM, Cassiano Leal wrote:

Seems relevant to add — I’m referencing the branch name:


application_ruby “resourcemanager” do

  …

  revision ‘develop’

  …

end


Could this be the source of my problems? If so, how do I fix it, or what should I be passing to ‘revision’ instead of the branch name?

It shouldn't matter how you specify the revision. If it's not a commit hash, the provider uses git ls-remote to figure out what the commit is, then uses that from then on.

Looks like the repo you get from `git clone` doesn't contain the SHA it's supposed to have, which is pretty odd since a subsequent `git fetch` picks it up. From the command line, with the same git version, does it fail if you 

COMMIT_ID = git ls-remote GIT_URL BRANCH
git clone REPO
git checkout -b deploy COMMIT_ID


-- 
Daniel DeLeo





Archive powered by MHonArc 2.6.16.

§