Upload a version only once


#1

Hi,

Is there a way to only ever allow a version of a cookbook to be uploaded
once. This would then force versions to be managed and help guarantee
reproducibility. I am thinking of what maven/nexus provides as an example
for this. It also seems to me that the notion of snapshot vs. releases would
be useful as well.

Cheers,

Florian


#2

You can freeze a cookbook. That will prevent new uploads without a version
bump. I like the knife-spork plugin for managing the freezing/bumping
process.

On Wed, Aug 21, 2013 at 10:49 AM, Florian Hehlen
florian.hehlen@gmail.comwrote:

Hi,****


Is there a way to only ever allow a version of a cookbook to be uploaded
once. This would then force versions to be managed and help guarantee
reproducibility. I am thinking of what maven/nexus provides as an example
for this. It also seems to me that the notion of snapshot vs. releases
would be useful as well.****


Cheers,****

Florian****


Brian Anderson | Operations Engineer
Phone 781.696.1304

www.affectiva.com
http://www.facebook.com/affectiva https://twitter.com/Affectiva
http://www.youtube.com/user/affectiva
http://www.affectiva.com/blog/ http://www.linkedin.com/company/affectiva_2
https://plus.google.com/b/115885368219797754125/115885368219797754125/posts


#3

Take a look at knife cookbook upload --freeze [1] and knife-spork [2]

-Nathen

[1] http://docs.opscode.com/chef/knife.html#upload
[2] https://github.com/jonlives/knife-spork

-Nathen

From: Florian Hehlen florian.hehlen@gmail.com
Reply-To: "chef@lists.opscode.com" chef@lists.opscode.com
Date: Wednesday, August 21, 2013 10:49 AM
To: "chef@lists.opscode.com" chef@lists.opscode.com
Subject: [chef] upload a version only once

Hi,

Is there a way to only ever allow a version of a cookbook to be uploaded
once. This would then force versions to be managed and help guarantee
reproducibility. I am thinking of what maven/nexus provides as an example
for this. It also seems
to me that the notion of snapshot vs. releases would be useful as well.

Cheers,
Florian


#4

On Aug 21, 2013, at 9:53 AM, Brian Anderson brian.anderson@affectiva.com wrote:

You can freeze a cookbook. That will prevent new uploads without a version bump. I like the knife-spork plugin for managing the freezing/bumping process.

My only issue with knife-spork was that it only worked with git repos (at the time I was trying to use it), and our codebase at that customer was in Subversion. So, knife-spork wasn’t useful to us.

But that was a while back, and I would hope that the plugin has progressed to support other repo formats since then. Other than that, it seems to me to be a really nice workflow tool.


Brad Knowles brad@shub-internet.org
LinkedIn Profile: http://tinyurl.com/y8kpxu


#5

Is there a way to only ever allow a version of a cookbook to be uploaded
once. This would then force versions to be managed and help guarantee
reproducibility. I am thinking of what maven/nexus provides as an example
for this. It also seems to me that the notion of snapshot vs. releases
would be useful as well.

+1 for snapshots vs releases!

See also http://tickets.opscode.com/browse/CHEF-4027


#6

Spork seems interesting indeed. But I am in the same situation as you. We
are using mercurial not git.

I find the tight coupling to git in the chef world a little annoying.
Version control should be an orthogonal concern. I am sure there are some
great arguments why the whole world should use git… but still :wink:

Cheers,
florian

-----Original Message-----
From: Brad Knowles [mailto:brad@shub-internet.org]
Sent: 21 August 2013 17:08
To: chef@lists.opscode.com
Cc: Brad Knowles
Subject: [chef] Re: upload a version only once

On Aug 21, 2013, at 9:53 AM, Brian Anderson brian.anderson@affectiva.com
wrote:

You can freeze a cookbook. That will prevent new uploads without a version
bump. I like the knife-spork plugin for managing the freezing/bumping
process.

My only issue with knife-spork was that it only worked with git repos (at
the time I was trying to use it), and our codebase at that customer was in
Subversion. So, knife-spork wasn’t useful to us.

But that was a while back, and I would hope that the plugin has progressed
to support other repo formats since then. Other than that, it seems to me
to be a really nice workflow tool.


Brad Knowles brad@shub-internet.org
LinkedIn Profile: http://tinyurl.com/y8kpxu


#7

On Wed, Aug 21, 2013 at 1:27 PM, Florian Hehlen florian.hehlen@gmail.comwrote:

Spork seems interesting indeed. But I am in the same situation as you. We
are using mercurial not git.

I find the tight coupling to git in the chef world a little annoying.
Version control should be an orthogonal concern. I am sure there are some
great arguments why the whole world should use git… but still :wink:

Cheers,
florian

It’s like more the side-effect of demand and motivation. Opscode uses
github and git. Most community cookbook contributors also use github (and
thus git). There have been several calls to provide, say, an hg provider
for the SCM resource but I don’t think anyone has stepped up to the plate.