Best practices for Source control


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Best practices for Source control
# 1  
Old 10-23-2009
Best practices for Source control

Hi all,
i am trying to incorporate source control management in my project. We have about 50 - 60 shell scripts on 3 different machines dev, stag and production, but there is no source control.

All the files have to be located at specific locations on each machine for it to work

I want to know whats the best practice to put this project into source control.
# 2  
Old 12-22-2009
If I understand your issue correctly you are looking for a distributed version control system? If so, then bzr, git, darcs, mercurial or monotone will help you? There will be one repository residing on one machine, from which the scripts are pulled by each of the other machines. Hope this helps.
# 3  
Old 12-22-2009
Source control is not software it is procedures, and then setting up the software to reflect those procedures.

You probably want a set of the associated archives: DEV, STAG, PROD - names don't matter.

Anybody can check out/ check in to DEV. After QA, the code is promoted to the STAG archive. This measn the code on the STAG box exactly matches what is current in the STAG archive. No exceptions. After more testing/papework/heartache the code is promoted to the PROD archive. A push to production is scheduled to coincide with promoting to PROD in the archive.

This is an example. Not best practices.

Short version:
Source control best practices
# 4  
Old 12-22-2009
I agree with Jim. Get your idea around the concept first and then find a tool (the software) that helps you implement it. You'll need to limit access to the STAG and PROD environment and have only those responsible for testing on the STAG box and those responsible for deployment on the PROD box. I don't know how detailed you want to get, but I work in a banking environment which is strictly controlled by the Fed, so controls, separation of duties and auditing is a part of daily life.

You can succeed at any level you what to, you just have to control those who don't want to get with the program. Smilie

Good luck
# 5  
Old 12-22-2009
I agree with the previous posters. Probably best to create a design document that also describes the requirements and the procedures. You may want to create a way of to deal with branches. I like subversion for script version control.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Linux

Virtualization best practices

Hello admins and gurus I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance -... (1 Reply)
Discussion started by: abohmeed
1 Replies

2. Solaris

Best practices

Dear all, Kinda lame question but i'd like to hear your experiences and advice. Question in short ----------------- What permission should a mount point "ideally" have - i think it's root. Ex:- /usr/app/ i'd set the app to be owned by root and within /usr/app i would create another... (1 Reply)
Discussion started by: ossupport55
1 Replies

3. UNIX for Advanced & Expert Users

emergency shutdown best practices.

Has anyone implemented or have suggestions on how to shutdown many remote unix/linux servers from a single script initiated from 1 server? I need this to execute in parallel as time is not on my side. Our ups is sadly underrated and will die in approximately 15 minutes. (There is not... (10 Replies)
Discussion started by: jsw371
10 Replies

4. UNIX for Dummies Questions & Answers

Scripting Best Practices

Hi - I am new to this and was wondering if some of you can help me out. I am just starting to write scripts and need some guidelines on creating scripts. I'm calling them "Best Practices"...what should I do and not do when creating scripts. All I know so far is that I should avoid putting... (5 Replies)
Discussion started by: toddjameslane
5 Replies
Login or Register to Ask a Question