Presentation is loading. Please wait.

Presentation is loading. Please wait.

Source Code Management Per Ahlberg Developer Evangelist Developer & Platform Evangelism Microsoft Sweden.

Similar presentations


Presentation on theme: "Source Code Management Per Ahlberg Developer Evangelist Developer & Platform Evangelism Microsoft Sweden."— Presentation transcript:

1 Source Code Management Per Ahlberg Developer Evangelist Developer & Platform Evangelism Microsoft Sweden

2 Agenda Overview of Team Source Control Comparison with VSS Features for Structured Process

3 Team Foundation Source Code Control 3-tier, web service architecture Built on SQL Server for robust, transaction- based version control Integration with other VSTS tools for automated workflow management Implementation of advanced SCM concepts Migrate from  VSS, ClearCase, Source Depot

4 Source Code Control Features Complete version control feature set  Uses Windows identities (rather than source control specific) for access. Innovative new SCC features  Integrated checkin  Parallel development  Atomic checkins  Remote development Integration with other VS Team System tools

5 3 Tier Uses SQL Server as a database  gives scale, reliability  excellent manageability: online back-ups, etc. ASP.NET web service middle tier  improves performance because process is done close to the data  enables tuned client/server protocol  protocols in addition to web services possible in future Variety of client interfaces  command-line, VS integration, etc.

6 Web Access Allows access over the public internet  doesn’t require RAS. Public web service protocol  allows integration and tools on other platforms Simple HTML based access  subset of functionality that allows rudimentary access from other platforms: get, check-out, check-in, history, etc.  not SourceForge or gotdotnet workspaces, etc in V1

7 Security Provides genuine security  there’s no back door Integrated with Windows authentication  use Windows users and groups to define identities  windows logon can authenticate clients Flexible ACL based security  fine grained ACLs: read, check-out, check-in, destroy, administer, etc. Roles define groups of permissions  simple set of default roles make administration easy: read- only, developer, administrator Most objects can be ACLed  not just files: workspaces, labels, etc.

8 Source Code Control Integrated Checkin Experience Combines changes, comments, work items, policy, e-mail Captures valuable data relationships Customizable for your process

9 Associate Work Items User Simply checks associated work items

10 Checkin Notes and Notification Entered at Checkin Time Defined per Team Project Included in Checkin E-mail Used in Build documentation as well Entered at Checkin Time Defined per Team Project Included in Checkin E-mail Used in Build documentation as well

11 Validate Policy Detail SCC Policy Engine Unit Testing WI Association Static Analysis Release Notes Custom Policy Policy Definitions.NET Assemblies Return Pass or Fail and message Customer Extensible User Over-ridable

12 Source Code Control Parallel Development Multiple Releases  Branching  Merging Multiple Checkouts

13 Source Code Control Shelving Interrupted workflow Transfer changes without checkin Checkpoint or share work in progress

14 Source Code Control Remote Development Remote development is a reality  Distributed teams, at-home, offshore A system built for the Internet  Web service protocols  Compatible with proxies and firewalls  Optimized for high-latency networks

15 Change Sets Expand notion of “checked out files” to “pending changes”  includes checkouts, adds, deletes, renames, etc. Higher level view of changes in the system  encapsulate all of the edits that make up a “logical change”  history of entire changes rather than individual files  unit for relationships: scheduling, bug tracking, etc Check-in of pending change set is atomic  guarantees everyone has a consistent view Change sets can be “parked” on the server  supports interrupted development, workflow, check-pointing, sharing changes, etc.

16 Off-line Support Pending changes can be created off-line  checkouts, adds, deletes, etc. Returning on-line is simple and quick  synchronizes client with server Some reporting features available  cache some data on client like local checkouts No off-line check-ins for V1

17 SourceSafe vs Team Foundation Visual SourceSafe 2005Visual Studio 2005 Team Foundation DescriptionVersion ControlIntegrated Software Lifecycle Suite Team SizeIndividuals and Small TeamsScalable StorageFile SystemSQL Server 2005 SecurityApplication specificWindows Integrated Remote AccessNew Web Service for VS Integration Optimized Web Service

18 Features for Structured Process Bug tracking integration Branching & merging Labels Workflow support/Extensibility

19 Bug Tracking Integration Relate bugs to change sets  enable traceability: find changes to fix a bug, find bugs that justified a change, etc. Modify bug status based on check-ins  resolve bug as part of check-in, approve change for “production” when bug closed, etc.

20 Branching & Merging “Cheap enough”  time and space to create a branch need not be a consideration Use SourceSafe/Source Depot branching model  branches identified by folder rather than “branch id” Branching and merging granularity is flexible  from individual files and change sets to huge trees Powerful merging  track partial merges  easily merge across multi-hop branches  diff and merge tools can be customized per file type Branches are manageable  easy to enumerate, remove, etc.

21 Labels Cheap for common point in time scenario Flexible for configuration management  file versions can be arbitrarily “tweaked” Easy to manage/scope  associated with particular files/folders Branches can be easily created from labels Label categories  Allow easy filtering of labels to avoid clutter from daily build labels, etc.

22 Workflow/Extensibility Server side extensibility  allows “triggers” on rich set of events  server side API available  published schema allowing extensions Client extensibility  events, client api, customizable components (editor, diff viewer, merge tool, etc.) Extensible check-in process  hooks to allow workflow: check-in review/approval, automated check-in (gauntlet), etc. Integration into bug tracking workflow

23 Summary Overview of Team Source Control Comparison with VSS Features for Structured Process


Download ppt "Source Code Management Per Ahlberg Developer Evangelist Developer & Platform Evangelism Microsoft Sweden."

Similar presentations


Ads by Google