DEV Windows --- QA & PROD Solaris

Our infrastructure Team requires few months to get us a Sun box so we are planning to use the Windows box for development. Then make *any changes* required to run the code on Solaris and check-in. Once the build is made QA will be done in Sun box and the same code will be promoted to Production on Sun box. (We got licenses for them.)

We need to hear from others about how this model worked/didn’t work with having development server on windows and QA & Production server on Solaris. (or in general different platforms)

Are these changes going to impact the development timeline?

We need this information ASAP to help us make a decision in the next couple of days.

Windows / Solaris 8 - TeamSite 6.5 SP2

Find more posts tagged with

Comments

nipper

Have done this, it is ugly.

98% of the stuff will work fine. If you write your perl correctly, that will be agnostic. However one big issue is that Solaris is case sensitive and DOS is not. so if you reference /iw/FormAPI/foo.js but the directory is /iw/FORMAPI/Foo.js then it will work in Dev and fail in QA. Same is true for your content.

Expect your QA process to be lengthened by this.

Also, what are you using for the presentation ? You will not get to test everything out in Dev since, if you had JSP, that won't work unless you are on a Solaris box.

Andy

nagendra

entries for inline commands in datacapture.cfg (like 'cat abc.txt') are different for each os. Testing server need to be on solaris and test cycle must be lengthy.
What about opendeploy receviers? some configuration files have attributes specific to os.

Ambuj

It's always good to have a similar environment for all three.. dev, QA and prod...

ASP will run on windows while JSP will run on sun.. there are other differences also in the code as mentioned above..

Also the user setup (OS user groups) are different in different environment..

Although you can use this design if you are ready to get rid of these all troubles...

Cheers,
Ambuj Smiley Happy