[chef] Re: Re: Re: Re: Application cookbook -- using Mercurial SCM provider


Chronological Thread 
  • From: Liam Kirsher < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Application cookbook -- using Mercurial SCM provider
  • Date: Tue, 04 Jun 2013 14:23:59 -0700
  • Openpgp: id=7011F7B7; url=http://liam.numenet.com/pgp/


On 06/04/2013 01:47 PM, AJ Christensen wrote:
" type="cite">
There's no mercurial provider. 
I saw this, which made me think there was a Mercurial provider --
https://github.com/opscode-cookbooks/mercurial/pull/5
I guess it wasn't merged?
" type="cite">
I notice you're using BitBucket, I
understand they support Git as well. I'm not sure if the two are
compatible in terms of talking to a single repository.
I haven't been able to find a way to use git to access mercurial without jumping through lots of hoops.
" type="cite">

You'll need to enhance Chef to be aware of Mercurial repositories (by
adding a Mercurial source code management provider), e.g. git [0],
subversion [1].

This could probably be added to the mercurial cookbook, which is
woefully lacking, the reason of which should be obvious (Git :P). [2]
I'm trying to avoid forcing a switch from mercurial to git.  People are religious about that kind of stuff.
If git's really required, then okay, but I'd like to see if Chef can use mercurial without too much trouble.
On the other hand, I don't want to get sidetracked with making Chef use mercurial when it would be possible to convert from mercurial to git.
" type="cite">

Cheers,

AJ

[0] https://github.com/opscode/chef/blob/master/lib/chef/provider/git.rb
[1] https://github.com/opscode/chef/blob/master/lib/chef/provider/subversion.rb
[2] http://ckbk.it/mercurial |
https://github.com/cookbooks/mercurial/blob/master/recipes/default.rb

On 5 June 2013 08:43, Liam Kirsher 
 
 "><
 > wrote:
The error is:
No provider found to match 'Chef::Provider::Mercurial'

On 06/04/2013 12:54 PM, Cassiano Leal wrote:
It would help if you included the error you're getting.

Guessing from the questions you asked, I'd say that the SSH key should be passphrase-less since Chef will run unsupervised.

-
Cassiano Leal


On Jun 4, 2013, at 16:50, Liam Kirsher 
 
 "><
 > wrote:

Hi --

I'm using the Application / Application_python cookbook to install Django.
The app source code lives in a Mercurial repo (which happens to be
private).
I need a little help here on how to do this.  This is what I've got, but
it's not working.

Does anyone have an example of how to do this?

How do I correctly reference the Mercurial provider?
I have verified that hg clone works with that url.
Does the ssh private key have to omit a passphrase?
I think the file referenced by deploy_key has to be uploaded somehow as
part of the cookbook.

application "bart" do
 path "/srv/bart"
 owner "nobody"
 group "nogroup"
 scm_provider "Chef::Provider::Mercurial"
 repository 
 
 /bart/server/bart">"ssh://
 /bart/server/bart"
 revision "master"
 deploy_key "/home/liam/.ssh/bti"
 migrate true
 packages ["libpq-dev", "git-core", "mercurial"]
Thanks!
Liam

--
Liam Kirsher
PGP: http://liam.numenet.com/pgp/


        
--
Liam Kirsher
PGP: http://liam.numenet.com/pgp/


    

-- 
Liam Kirsher
PGP: http://liam.numenet.com/pgp/



Archive powered by MHonArc 2.6.16.

§