Closed peterabbott closed 9 years ago
Let me see if I can get the old version populated on the new site before we merge this. Would that work for you?
the easiest short-term solution would be tag version 0.2.0 from the commit before the new updates were pushed to master. That way we can add a tag attribute to our Berkshelf files to pull the older version. That would give you time to decide if you want to put the older versions on the new repo.
Ok, I just realised that in the Berksfile I can use a revision number as the ref attribute
For example, this points to a previous revision before the repo location update. Will use this solution for now, but perhaps the tagging of v0.2.0 would still be useful
cookbook "go", git: "https://github.com/ThoughtWorksInc/go-cookbook.git", ref: "50a6cfcfd3f8722fb15a517a34394ed9949d079b"
@peterabbott thanks for the help on this one.
The new repo locations now contain the last 13.x release, and I've created a v0.2.0 branch too.
The update will check the version attribute, if is 13.x.x.x it will use the old repo, otherwise the new one is used.
There is an additional version 13 test with test-kitchen to verify the use of an older repo. The version string is added to the agent defaults file as a comment to be able to easily determine the version of the agent.
Default test has been updated to test for the current default version 14.2.0-377.