1. Intro
2. Which Repository?
3. Ten Commandments
3.1 Thou shalt not break the build
3.2 Thou shalt do an update before a commit.
3.3 Thou shalt practice theoretical coding
3.4 Thou shalt implement a continuous integration server
3.5 Thou shalt trust thy merging tool
3.6 Thou shalt tag and tag in moderation
3.7 Thou shalt minimize the duration and amount of branches
3.8 Thou shalt commit changes daily
3.9 Thou shalt run tests on code
3.10 Honor thy assets by committing all related material
4. Access
4.1 TFS Levels
4.1.1 Stakeholder
4.1.2 Basic
4.1.3 VS Enterprise
4.2 SVN Levels
4.2.1 SVN ACCESS MANAGER
4.2.2 TortoiseSVB
5. Training
5.1 Video
6. New Repository Request
7. Application List
8. Version Control
8.1 Version Numbering
8.2 Basic Work Cycle
8.3 Create a working Copy
8.4 Update Your Working Copy
8.5 Make Your Changes
8.6 Review Your Changes
8.7 Fix Your Mistakes
8.8 Resolve Any Conflicts
8.9 Commit Your Changes
9. Branching
9.1 What is a Branch
9.2 Basic Merging
9.3 Keeping a Branch in Sync
9.4 Branch Types
9.4.1 Release Branches
9.4.2 Feature Branches
9.4.3 Vendor Branches
10. Builds
10.1 Mechanisms in Continuous Integration
10.2 Key Principles of Continuous Integration
10.3 Continuous Integration With Jenkins
10.3.1 Orchestrating Your Delivery Pipelines with Jenkins
11. Best Practice
11.1 If it’s not in source control, it doesn't exist
11.2 Commit early, commit often and don’t spare the horses
11.3 Always inspect your changes before committing
11.4 Remember the axe-murderer when writing commit messages
11.5 You must commit your own changes – you can’t delegate it
11.6 Versioning your database isn't optional
11.7 Compilation output does not belong in source control
11.8 Nobody else cares about your personal user settings
11.9 Dependencies need a home too
12. Glossary
13. References
About
Title
Code Source Control
Subject
-
Company
-
Author
Mindjet
Version
31
Comments
This is a blank template. This classic mindmap layout allows subtopics to be organized on both sides of the central topic.