On Thu, Sep 22, 2011 at 9:20 AM, sauer wrote: > Forum: CFEngine Help > Subject: Re: OS patch management -- how to deploy the same patch set to > production as you did to testing 3 weeks ago? (How to "take a snapshot" of an > OS patch set) > Author: sauer > Link to topic: https://cfengine.com/forum/read.php?3,23563,23579#msg-23579 > > We just configure a "test" and "production" local mirror. When we are ready > to deploy an updated package to the test environment, we copy the package > into the test repo. Once it's ready for production, we copy it into the > production repo.
I got similar answers from the CentOS community. (See below.) I also want to acknowledged the RPath and Red Hat Network Satellite Server answers I got on this list (Paul and Tom), thank you. On Fri, Sep 23, 2011 at 6:35 AM, Johnny Hughes <joh...@centos.org> wrote: > > There is no solution to do updates that are different than the mainline > tree, except to maintain your own repo. > ... > Of course, this puts the burden of testing and maintaining that repo on > you ... but you are the only one who can decide how much testing is > enough and what needs to be tested before you move a new RPM (or set of > RPMS) into production. On Thu, Sep 22, 2011 at 12:24 AM, Trey Dockendorf <treyd...@gmail.com> wrote: > I think a local mirror is really your best option. Or possibly two repos. > One for testing, which you sync when you want to test updates and point all > test systems at it. Then a production repo for production systems that > pulls from the frozen test repo. One addition to your idea would be to use > git. That way all you have to do is a 'git push' when you want to update > your production repo. Could then use other features in git for tracking > changes, possible reverts and such. Best, -at _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
