Giving Devs a Dev platform

It's a typical situation, the developers develop on their own boxen, they only start to integrate their code on on the production platform 3 hours before the deadline. And then the problems start, the typical "But it works on my system" , "its your problem now" is something nobody really likes to hear .

So how do you tackle this problem ? As Christian already mentions Talking is the first step of the solution,

But one of the most satisfying approaches to solve this problem is to provide your development teams with a standard platform that you support, and a platform they can play with , if you can't provide them with a fully defined platform, give them a set of guide lines on what they can expect. Things like library versions, database types , memory availability and storage availability are key components of such guidelines.

My platform of choice for this kind of projects today is to for an Enterprise Level distro, a distro that stays stable for a longer period, not one that is bleeding edge and changes every other week. So a CentOS or a Debian based distro is probably going to be the platform of choice. But a stable standard platform also means that all the latest nice features a developer wants to have from the bleeding edge libraries he is using aren't going to be available .

Sometimes your devs really need those features, sometimes its just a nice to have. On the other hand you as an ops guy don't want to be packaging and configurating every single tool they dream off. As usual in a Devops environment the key can be found in communication ... Talking with the devs will teach you what features they really need and how they might solve things in a different, more standardized way

We've learned that by giving them a default platform and keeping an open conversation helps, some developers take longer to understand the process others jump in right away .. but in the long term you really need to talk to your devs as soon as possible when they think of implementing a new project that has to run on your platorms.

Lets you sleep at night ..


Leo's picture

#1 Leo : Or you read my article in the

Or you read my article in the Open Horizons Magazine of Autumn 2009 ;-)

Kris Buytaert's picture

#2 Kris Buytaert : The What ?

Apparently I didn't ....

Leo's picture

#3 Leo : Appliances

Using Appliances (e.g with Suse Studio) can be a good solution for this.

Providing an appliance to your developers gives them the exact same environment as they would have in production.

I know of a big dutch bank who does it this way.

Kris Buytaert's picture

#4 Kris Buytaert : talk

I can only assume that you have indeed seen my presentation on building virtual Appliances :)