There’s no mercurial provider. 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.
You’ll need to enhance Chef to be aware of Mercurial repositories (by
adding a Mercurial source code management provider), e.g. git ,
This could probably be added to the mercurial cookbook, which is
woefully lacking, the reason of which should be obvious (Git :P). 
 http://ckbk.it/mercurial |
On 5 June 2013 08:43, Liam Kirsher firstname.lastname@example.org 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.
On Jun 4, 2013, at 16:50, Liam Kirsher email@example.com wrote:
I’m using the Application / Application_python cookbook to install Django.
The app source code lives in a Mercurial repo (which happens to be
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
packages [“libpq-dev”, “git-core”, “mercurial”]