General discussion about Chef

[chef] Berksfile.lock commit in dev branches


Chronological Thread 
  • From: "Hajducko, Steven" < >
  • To: " " < >
  • Subject: [chef] Berksfile.lock commit in dev branches
  • Date: Wed, 11 Feb 2015 20:25:11 +0000
  • Accept-language: en-US
  • Authentication-results: lists.opscode.com; dkim=none (message not signed) header.d=none;
  • Domainkey-signature: s=default; d=intuit.com; c=nofws; q=dns; h=X-SBRS:X-IronPort-AV:Received:Received:Received:Received: From:To:Subject:Thread-Topic:Thread-Index:Date:Message-ID: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:x-originating-ip: authentication-results:x-microsoft-antispam: x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:Content-Type:MIME-Version: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id: X-MS-Exchange-Transport-CrossTenantHeadersStamped: Return-Path:X-OriginatorOrg; b=hFZiY8asyw8qEY6PvGubodfHiwW/pJlRKrSMP12aXI1QjfcHrCvidKaV YBstEnXjCdxFHJ33mDpcSxV69+tBAY7HNTwdPw8gT1Ubu7Q6mxwfbVsBU N2jAN44KF4uLqALU+zOQOmKee629KMDwjHnOkWwukjOdpEIjS+2yWqP/P M=;

We've been having a discussion lately about whether to include Berksfile.lock in our dev branches for our cookbooks.  Right now, I've only been including them in the stable branch. I've seen several other threads ( not on this list ) about this and opinions seem to be back and forth.  Also, since the berks generators put Berksfile.lock into the .gitignore, it seems the opinion of Berks is to *not* include them.


I see the advantage of including them in the dev branches as providing an identical environment for anyone collaborating on the cookbook - but it seems like the Berksfile itself and the metadata.rb constraints should be enough to provide a 'close enough' environment.


What are the disadvantages of including the lock files?​  What do you typically do for your cookbooks?




Archive powered by MHonArc 2.6.16.

§