From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Halstead, Robert
Sent: Monday, September 25, 2006 10:12 AM
To: [email protected]
Subject: Re: Best ways to rollout new features.
Bob Halstead
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of McKenzie, James J C-E LCMC HQISEC/L3
Sent: Monday, September 25, 2006 11:04 AM
To: [email protected]
Subject: Re: Best ways to rollout new features.
Bob:
Packing lists are the way to go if you are upgrading an existing server. I would, however, backup my entire database instance before doing an upgrade through this method. Again, I would also try this on the test server before attempting to do this on the production system. (I cannot emphasize this enough.)
James McKenzie
L-3 GSI
-----Original Message-----
From: Action
Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of
Halstead, Robert
Sent: Monday, September 25, 2006 9:45
AM
To: [email protected]
Subject: Re: Best ways to rollout new features.
We are using v6.03. I've looked at the packing list object but didn't fully understand what it was used for. Class didn't cover it too much (least not 2nd part Adminstrator class). Can anyone point me to a link that explains this object? If I can get away with using a packing list that would be awsome =)
Bob Halstead
-----Original Message-----
From: Action
Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of
Carey Matthew Black
Sent: Monday, September 25, 2006
10:38 AM
To: [email protected]
Subject: Re: Best ways to rollout new features.
Robert,
I am not sure why you felt the need to "by exporting the form and importing it on production one at a time". Maybe you had some "good reason" for that?
Also ARS Server Version matters a bit here too. If you are post
...
v5? (definitely v6) then there is an import in place
option during the import to production that you should fully understand before
you plan how to do your release management too.
I would also suggest that you look at the Packing List object. If you can identify all objects that were changed on the dev server for a given release then you can add them to a Packing List and use that arbitrary list as a "package" of changes.
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action
Request System(Remedy)
Love, then teach
Solution = People +
Process + Tools
Fast, Accurate, Cheap.... Pick
two.
On 9/25/06, Halstead, Robert <[EMAIL PROTECTED]>
wrote:
> **
>
> Sorry if someone has posted this before, I'm new to the
list. I was
> wondering if there is a good way
to rollout new features and
> enhancements to
existing forms? We have a test box that we do all of
> our development work on and then push it to the production
box. Since
> we are new with remedy we've only done this once with some
> complications by exporting the form and importing
it on production one
> at a time. Is there was some type of way to rollout
everything at
once in some sort of package?
>
>
>
> Bob Halstead
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist
Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
