We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Segregating developer access to production

Medium Priority
1,013 Views
Last Modified: 2013-12-05
will revision control software, such as Perforce, provide segregation of duties (i.e., prevent developers from accessing production)? Or is it just to protect the code repository and log what changed?
Comment
Watch Question

MIS Liason
CERTIFIED EXPERT
Most Valuable Expert 2012
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
Thank you for the response. You answered the specific question I posed.  To expand,  I'd like to find out if anyone out there has used Perforce beyond revision control?  I believe that it has broader application, as explained by their literature.  I'd specifically like to know if it can be employed to prevent migration of code to the production environment by certain groups/users.  If anyone has used it in this fashion, I would like to know its full capabilities, apart from the company's claims.  Thanks.
Scott McDaniel (EE MVE )Infotrakker Software
CERTIFIED EXPERT
Most Valuable Expert 2012
Top Expert 2014
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
Scott McDaniel (EE MVE )Infotrakker Software
CERTIFIED EXPERT
Most Valuable Expert 2012
Top Expert 2014

Commented:
BTW, I believe you posted this in the Microsoft Access TA by chance ... you might have the Mods change your TAs to more suitable ones, as few Experts here in the Access TAs will have worked with Perforce. Click the "Request Attention" link.
Jeffrey CoachmanMIS Liason
CERTIFIED EXPERT
Most Valuable Expert 2012

Commented:
pellero1000,

Oh, and as far as needing to set the DB to work in one mode for developers and one mode for users, you can create a small Login system for this.
Create a table with the users Name, password, and "Status".
User status can be either "Developer" or "User"
Then show/Hide certain features based on the user's status.

LSM is great at things like this.
But, you may want to post a separate question on this though.

JeffCoachman
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.