Discussion posted 3/28/08 by Serenity Thompson
Details:



supportadmin

Topic: Promote after Baseline (1 of 4), Read 46 times
Conf: ZMF
From: Steve King StevenR.King@Caremark.com
Date: Wednesday, April 04, 2007 08:10 AM
Originally Posted 4-Apr-2007 08:08
Can a ChangeMan package be promoted after it has been 'baselined'? is there any option or customization for this? Do you know of any customers who do this? We may be looking into this option in the future.....The only three things that I could think of was A) Create new packages with the same components in as the "BAS" packages; and then promote to the post-prod environment; or B: When ChangeMan is down, change the status on the "BAS" packages to 'FRZ' on the package master to allow for the promote to this environment; and then change back to "BAS", but this option sounds dangerous; or C) Add more steps to the CMN30 install skel to do the promote, but have the job sit in SDSF on hold until the post prod move is ready to go.
Topic: Promote after Baseline (2 of 4), Read 39 times
Conf: ZMF
From: Miguel Nevarez Miguel.Nevarez@gmacinsurance.com
Date: Thursday, April 05, 2007 08:50 AM
Question, why would you actually want to do this? The cleanest way would would create a package and checkout the components that were baselined. The only reason you would want to change any status of a package is if you encountered a problem with that package. Normally I get rid of problem packages.
With some customization and preventing the package from being cleaned up when baselining would work.
Topic: Promote after Baseline (3 of 4), Read 46 times
Conf: ZMF
From: Steve King StevenR.King@Caremark.com
Date: Thursday, April 12, 2007 07:56 AM
The reason someone here was thinking about doing this was to promote to a stable test environment after the package has be 'baselined' for post user testing. Creating a new package was an option I considered (probably the cleanest option) and this option would require the most work, about 120 packages each month. I am trying to convince them to promote to a new test environment just before the package is 'baselined'. Hopefully they will listen. Thanks for your comment.
Topic: Promote after Baseline (4 of 4), Read 17 times
Conf: ZMF
From: Glenn Dove gdove@jasmattcorp.com
Date: Tuesday, May 15, 2007 05:44 AM
If your configuration is a DP/P, you can set up the additional promotion level as a SITE and then install into it as well as your P site. You can even use CMNEX039 to "group" the site names into a single site that would only be used by the application that needs it. Then you will still only see one site in the Package Create process. If you're an A site, this is a little more difficult and I would agree with the previous response of promoting to that level at final approval time and make sure the baseline ripple process doesn't clean up that level when it runs.
Posted 5/30/2007 5:51 PM





tmavor

To add to Glenn's point there might be good reasons to do the reverse -- ie -- install into a preproduction test area before going live to production -- That would fit the best practice model. ie -- for all intense purposes the final test area should be as clean as possible with full back out capabilities.
This was done a lot during the lead up to Y2K -- remember that time. The final test area in question was known as the Y2K box. Yes some shops promoted to this box but many also installed to it before going to actual production. The more mature a shops processes the easier it is to use this methodology.
If you are still find a lot of program bugs this late in the process it might not be the best way to go.
Posted 6/6/2007 9:45 PM

#post5df5fd3520
#oldforumpost
#ChangeManZMF