Comments on: Access controls in test environments http://www.build-doctor.com/2009/01/11/access-controls-in-test-environments/ Continuous Integration, Delivery and Devops Consulting Thu, 02 Feb 2012 22:31:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: How to Avoid Auto Deployments Behaving Badly « Developing Code, Connecting Industryhttp://www.build-doctor.com/2009/01/11/access-controls-in-test-environments/comment-page-1/#comment-713 How to Avoid Auto Deployments Behaving Badly « Developing Code, Connecting Industry Fri, 18 Dec 2009 14:01:30 +0000 http://www.build-doctor.com/?p=418#comment-713 [...] operations, Point2, systems, testing A couple of posts relating to development/ops gaps, and access control reminded me how very far we have come with our environments over the past few [...] [...] operations, Point2, systems, testing A couple of posts relating to development/ops gaps, and access control reminded me how very far we have come with our environments over the past few [...]

]]> By: simpsonjulianhttp://www.build-doctor.com/2009/01/11/access-controls-in-test-environments/comment-page-1/#comment-271 simpsonjulian Mon, 19 Jan 2009 10:10:07 +0000 http://www.build-doctor.com/?p=418#comment-271 As a sysadmin I don't mind that the user has to elevate privilege to get root. It means that you can actually see who is doing what to your environments. This isn't as good as being able to rebuild at will, of course. I'd love to go down there and play the '5 whys' game ... ! As a sysadmin I don’t mind that the user has to elevate privilege to get root. It means that you can actually see who is doing what to your environments. This isn’t as good as being able to rebuild at will, of course.

I’d love to go down there and play the ’5 whys’ game … !

]]> By: Neilhttp://www.build-doctor.com/2009/01/11/access-controls-in-test-environments/comment-page-1/#comment-270 Neil Fri, 16 Jan 2009 14:46:16 +0000 http://www.build-doctor.com/?p=418#comment-270 Interesting because at the place I work (a well known media company) we're getting quoted SOX everytime we request access to any test and development environments. Dev environments here are the old fashioned kind that people share, can't be rebuilt, are not baselined and approximate production (just). And they've chucked a new spanner into the works called credit card industry compliance. What this all means is that we can't have password to generic userids such as a build user, or oracle user. Every interaction with these accounts has to be via sudo and sudo su. The solution is to have local development environments of course but this company kick off projects and discover they don't have the right development environments 6 months down the line! Interesting because at the place I work (a well known media company) we’re getting quoted SOX everytime we request access to any test and development environments. Dev environments here are the old fashioned kind that people share, can’t be rebuilt, are not baselined and approximate production (just). And they’ve chucked a new spanner into the works called credit card industry compliance. What this all means is that we can’t have password to generic userids such as a build user, or oracle user. Every interaction with these accounts has to be via sudo and sudo su. The solution is to have local development environments of course but this company kick off projects and discover they don’t have the right development environments 6 months down the line!

]]> By: Dan Ackersonhttp://www.build-doctor.com/2009/01/11/access-controls-in-test-environments/comment-page-1/#comment-269 Dan Ackerson Wed, 14 Jan 2009 22:16:27 +0000 http://www.build-doctor.com/?p=418#comment-269 Nice one, Julian! It's never easy doing the right thing but I'm sure your persistence paid off in the long run. Too many cooks in the kitchen <strong>will</strong> ruin the soup! Nice one, Julian! It’s never easy doing the right thing but I’m sure your persistence paid off in the long run. Too many cooks in the kitchen will ruin the soup!

]]>