What I have done is set up two different profiles with normally identical contents. One profile is for production machines and one is for my test machine. In the hosts.xml I have the test machine host assigned to the test profile. When I want to test something I change the profile definition and restart the wpkg service on the test machine (I have a powershell script which I use for this). If everything is good, I then change the production profile to match the test profile.
________________________________ Kind regards, Bill Prentice -----Original Message----- From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-boun...@lists.wpkg.org] On Behalf Of Jason Oster Sent: Monday, 21 December, 2009 09:50 To: wpkg-users@lists.wpkg.org Subject: Re: [wpkg-users] test packages upgrades On 12/20/2009 01:44 AM, Andrea Zagli wrote: > how can i do to test packages upgrades on only one test machine before > to propagate the upgrade to all others production machines? > > thanks in advance I've been meaning to set up a second share directory on my Samba server with WPKG packages. My test workstation would check-in with that directory instead of the normal one. Use symlinks for the software and most of the XML packages; use real files only when testing. I don't have detailed information, sorry. But there is more information on this kind of idea in the list archives somewhere! Good luck ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
