On 6/3/2010 3:00 PM, [email protected] wrote:
Message: 6
Date: Wed, 2 Jun 2010 17:30:53 -0700
From: "Boydell, Stuart"<[email protected]>
To: U2 Users List<[email protected]>
Subject: Re: [U2] SB+ PA Compare
Message-ID:
<7ee7790a950e094399b01520071826a20106b48d6...@sg1rd3xvs031.red003.local>
Content-Type: text/plain; charset="us-ascii"
Hi Steve,
Perforce for source control combined with virtual machines for development and
test.
The use of Perforce was mainly because it has a great API and fits well with
the spectrum of development. It's not all about U2 here.
I haven't looked at any of the distributed VCS components so I can't offer any
advice there.
As a suggestion, I cannot recommend highly enough the use of VMs for dev and test. Using
a VM will give you a system based replication of your production environment and data.
This means rather than creating development and test accounts, you can develop and test
in your "production" environment with all the same file pointers, account
names, security settings etc.
There are numerous other advantages to VMs. They can be provisioned and torn
down again rapidly. Depending on your VM platform they can be snap-shot and
rolled back during bug fixing, install dev/tests and scenario testing. You can
have an app developed and installed with*exactly* the same set of artefacts
and instructions for test and prod. And it also which means you can reduce the
number of accounts you need to maintain.
Cheers.
S
I would love to use vm's, however, we are using udt on aix. there isnt
any guest ability for aix :). I could maybe use rhel test accts, but
the conversion of files each time could be a problem. The endian
problems, etc.
For those Prelude users out there, I did hack up a PSICOPY that uses
rsync so I can psicopy remotely. That still wont help with the
conversion issues of mixing x86 and ppc.
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
