Environment Control

Over the past few weeks I’ve been working on new project to create a new content management framework within Reddot. I’ll probably blog about the implementation and the challenges around this project in other blogs later on but for now I will focus on the issue of environment control.

Issue: 12 Bugs in QA – this just isn’t acceptable.

Solution: To help reduce this were implementing a new process inline with what we would do if we where working of sourcesafe and using crusie control to our builds. All the CSS, JavaScript and Images (and later on .NET code when we come to it) are being put into sourcesafe. We have created separate DEV and INT environments which we only deploy from a cruise control build and then release the reddot pages to that environment (this is managed by a Build Engineer). The development work which used to be done in the DEV environment is now done on a developers machine this allows viable DEV testing to take place. Along with better testing pratice and more stringent gates on our Scrum board I’m hoping the next release will run much smoother.

I’ll keep you posted on this

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: