Anyone doing cummulative update packages?

LoriStephens

Well Known Member
Hi,

I have a request. My first CNC Consultant told me to do cummulative
updates. Now I have another CNC Consultant telling me I shouldn't be doing
them. Question is: Are you doing cummulative updates? Why or Why not?

I realize now there could be a problem in the development pathcode if they
are changing things regularly. But why not do it in the others?

Thank you!

Lori
OW Xe SP16 Update 2
AS400 V5R1 NT
Citrix
email: [email protected]
 
I do incremental update packages then re-compress the parent package which updates the parent package.cab files with the latest update package.

Patty

B733.1\SP7.1\Oracle 8.0.5\Ent HP-UX 11.0

Upgrading to XE\SP15.1\U3
 
Lori,

please define what you mean by cumulative update. I have an idea what you mean, but let's be sure we're talking about the same thing.

Cheers,

Larry Jones
[email protected]
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials
 
Larry,

Cumulative updates are when you take the previous update package, copy it
and add the projects(objects) you want to be in your package. Then when you
build the update package it includes all from the previous updates and the
new stuff.

:) Lori






Lori
OW Xe SP16 Update 2
AS400 V5R1 NT
Citrix
email: [email protected]
 
I've tried it both ways and I find that stand alone update packages with
periodic FULL packages is the best and safest way to go.

With OMW working the way it does and us having to check-out / get the
latest code before assembling a package from a FAT client and then building
on the Deployment server, I found that incremental (if I understand how you
are using this term) was too much work. I build update packages for
whatever needs to go for that day (or since the last update package). When
I have a number of these update packages or a significant number of objects
built within them I then build a full package and start the cycle over
again.

I have gone and recompressed the parent package again to incorporate the
update packages into the parent that they are built against but I have run
into problems where an update package contained fixes for one problem but
caused a more serious problem in other areas of the system. If you
recompress the parent package with the update package fixes then you can
corrupt the parent package as well... then how do you back out easily?
Granted there is a backup/restore option for ESU's but not for development
objects your guys create.

Bottom line for me is that I build a Full package, then subsequent update
packages as required with only the objects needed for that update build -
not cumulative - and when I get enough of them I build a new Full package
again. Yes this means that for every new client I install I have to
install the full package and every update to bring the client current, but
if there is a problem with the objects in any update package I can easily
remove it from a client by simply reinstalling the good packages - no
messing with source code until a proper fix is found. Of course having a
small number of Fat clients helps this process too.

I hope this helps.

Regards,
Gerald.








LoriStephens
<jdeperson@hotmai To: Gerald Kastanek/Toronto/IBM@IBMCA
l.com> cc:
Sent by: Subject: Anyone doing cummulative update packages?
owner-jdelist@jde
list.com


04/04/2002 04:37
PM
Please respond to
jdelist






Hi,

I have a request. My first CNC Consultant told me to do cummulative
updates. Now I have another CNC Consultant telling me I shouldn't be doing
them. Question is: Are you doing cummulative updates? Why or Why not?

I realize now there could be a problem in the development pathcode if they
are changing things regularly. But why not do it in the others?

Thank you!

Lori
OW Xe SP16 Update 2
AS400 V5R1 NT
Citrix
email: [email protected]





--------------------------
 
Lori

I re-compress after every update package, then burn a CD of the full package. This way if a machine needs to be installed/re-installed the full package is up-to-date. Our pc guys can install off of CD or pull it straight from the deployment server.

Patty

B733.1\SP7.1\Oracle 8.0.5\Ent HP-UX 11.0

Upgrading to XE\SP15.1\U3
 
Lori,

I manage my packages exactly as Gerald does, and for many of the same reasons! I like to know exactly which package is going to deliver specific changes.

I also noticed that you use Citrix, as I do. Are you in control of your Citrix installs? If I need to reinstall from scratch, I find that reinstalling, let's say, 1 full and 5 updates (usually the magic numbers for me before I build a fresh full) is not much slower than using recompression options to update cabs and deploy fewer packages. Fast citrix servers and backbones can run through the installs fairly quickly. In my environment, the very minimal time savings does not carry the benefit of sticter version tracking.

Regards.

Ryan Hunt
OneWorld XE; Update2; SP17.1_E1
AS400; V4R5
DS: Win2k SP2, SQL 7.0 SP3
TSE's: Win2k(SP2) & NT4.0(SP6a) with Metaframe 1.8
 
OK,

why do a cumulative unless your updates are not mandatory and/or not deployed everyewhere?

FYI if you don't use compression on your packages then your full package is automatically updated by each update package. Works good and saves on a lot of admin time.

Larry Jones
[email protected]
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials
 
Larry, good question about the cumulative update. Although, I think one reason would be if you were doing FREQUENT fat client installs. This way your installers could simply install one full and one update at all times and get the most current code. Or, if you do not compress the parent package as you stated, you could simply install just the one full client for that matter.

One thing to be carefull of (and why I compress packages, but do not recompress). If you install a software update and build an update package that completely ruins an app or apps, you cannot immediately install the full and updates up to the last to resolve the issue while you find the more permanent repair. Your uncompressed parent package is now a carrier of your problem.

Anyway, there are many ways to do this CNC thing! This is just one flavor. ;-)

Regards.

Ryan Hunt
OneWorld XE; Update2; SP17.1_E1
AS400; V4R5
DS: Win2k SP2, SQL 7.0 SP3
TSE's: Win2k(SP2) & NT4.0(SP6a) with Metaframe 1.8<P ID="edit"><FONT SIZE=-1>Edited by rhunt01 on 4/5/02 12:50 PM.</FONT></P>
 
Ryan, yes, I control all installs. Thanks very much for your reply. I'm
mulling all of these ideas over... I agree with your 'magic number'.

:)


Lori
OW Xe SP16 Update 2
AS400 V5R1 NT
Citrix
email: [email protected]
 
Back
Top