Source Control Systems Brick

ITS Technical Architecture - Brick   

Source Control Systems

Primary Architect:  Cameron Ahana

Description:   

Source Control Systems allow developers to manage their source code.  Key features include: version control and the the capability to check-in and check-out code.  Source Control Systems are not only used by application developers but can also used by system administrators and database administrators to manage scripts and configuration files.

Many Source Control Systems are cloud-based which open the possibility of easily sharing code with developers outside of the institution. This of course introduces other challenges as well.

ITS originally used CVS for source control, and started to migrate to GIT (Gitosis) in 2007.  In 2016, limitations with Gitosis led ITS to look for an alternative.

Emerging Trends

• Mercurial, Git, etc are DVCS (Distributed Version Control Systems) that have gained in popularity in recent years. Allow developers to “check-in” on their machines when away from internet connection.

• Microsoft Visual Studio and VisualSourceSafe are popular with Microsoft developers

• Updated and re-approved (September 2016)

• Added version numbers and a notes section detailing the organization pricing plans for GitHub and BitBucket (2014)

• Brick first created July 2014

Definitions