WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.

Slides:



Advertisements
Similar presentations
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Advertisements

WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Version Control CS440 – Introduction to Software Engineering © 2014 – John Bell Based on slides prepared by Jason Leigh for CS 340 University.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Version Control What it is and why you want it. What is Version Control? A system that manages changes to documents, files, or any other stored information.
Patterns & practices Symposium 2013 Introducing Git version control into your team Mark
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Version Control with git. Version Control Version control is a system that records changes to a file or set of files over time so that you can recall.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
With Mercurial and Progress.   Introduction  What is version control ?  Why use version control ?  Centralised vs. Distributed  Why Mercurial ?
Git – versioning and managing your software L. Grewe.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Source Code Control CSE 3902 Matt Boggus. Source code control options for CSE 3902 Must use source code control that is integrated with Visual Studio.
ITEC 370 Lecture 16 Implementation. Review Questions? Design document on F, feedback tomorrow Midterm on F Implementation –Management (MMM) –Team roles.
Source Control Primer Patrick Cozzi University of Pennsylvania CIS Spring 2012.
2010. The Subversion Dilemma Check in buggy code and drive everyone else crazy Avoid checking it in until it’s fully debugged or.
Version Control. How do you share code? Discussion.
Git workflow and basic commands By: Anuj Sharma. Why git? Git is a distributed revision control system with an emphasis on speed, data integrity, and.
Information Systems and Network Engineering Laboratory II DR. KEN COSH WEEK 1.
Object-Oriented Analysis & Design Subversion. Contents  Configuration management  The repository  Versioning  Tags  Branches  Subversion 2.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
1 GIT NOUN \’GIT\ A DISTRIBUTED REVISION CONTROL AND SOURCE CODE MANAGEMENT (SCM) SYSTEM WITH AN EMPHASIS ON SPEED. INITIALLY DESIGNED AND DEVELOPED BY.
Version Control Systems. Version Control Manage changes to software code – Preserve history – Facilitate multiple users / versions.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Version Control System Lisa Palathingal 03/04/2015.
Source Control Saves Lives. Lorna Mitchell Source Control Saves Lives BarCamp Leeds What is Source Control? Central filestore Change history Audit trail.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Version Control and SVN ECE 297. Why Do We Need Version Control?
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Introduction to Git - Chirag Dani. Objectives Basics of Git Understanding different “Mindset of Git” Demo - Git with Visual Studio.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
1. A new git is initialized as a remote repository JohnRemote repositoryPeter master C0 CodingWhileBlack.com PROPEL CODING
Git A distributed version control system Powerpoint credited to University of PA And modified by Pepper 28-Jun-16.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Collaborative Git An introduction to Git with others
GIT Version control. Version Control Sharing code via a centralized DB Also provides for Backtracking (going back to a previous version of code), Branching.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010/2013.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Git primer Landon Cox January 19, 2017.
4 Version control (part 1)
45 min WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint.
Git and GitHub primer.
Version Control.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Storing, Sending, and Tracking Files Recitation 2
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Patrick Cozzi University of Pennsylvania CIS Fall 2012
Git GitHub.
Presentation transcript:

WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint They may not show up well on other PowerPoint versions. You can download PowerPoint 2010 viewer from here.here These slides contain a lot of animations. For optimal results, watch in slideshow mode.

A success story: Damien is working for a technology startup. He is part of a 5-member team, all good buddies of each other and work was fun. It was a critical project for a major overseas client. The product is a novel proof-of-concept proxy server. As the team enters the last two weeks of the project, they are one week ahead of schedule and has one week allocated for integration and testing. i.e., they have two weeks to do the work of one week. They decide to do a quick integration and take the extra week off to celebrate the first release…

UI MSLogic Storage History UI MSLogic Storage History

Due to miscom

How to Avoid a Big Bang: Integrating Software Components CS2103/T, Lecture 6, Part 2, [Sep 20, 2013]

How to Avoid a Big Bang: Integrating Software Components CS2103/T, Lecture 6, Part 2, [Sep 20, 2013]

[Extra] Integration Work in parallel Logic UI Search Cache Storage Integrate Search Logic Cache Storage UI

Logic UI Search Cach e Storage Logic UI Search Cache Storage Logic UI Search Cache Storage Search Logic Cache Storage UI Late and one-time Integration

Logic UI Search Cach e Storage Logic UI Search Cache Storage Logic UI Search Cache Storage Early and frequent Integration

Late and one-time Integration

Early and frequent Integration Late and one-time Integration ?

Early and frequent Integration Late and one-time Integration

Early and frequent Integration Late and one-time Integration

Logic Search Cache Storage UI Logic Search Cache Storage UI Search Logic Cache Storage UI

[Extra] Top-down Integration Logic Search Cache Storage UI Logic Search Cache Storage UI Cache Storage Stubs

[Extra] Bottom-up Integration Logic Search Cache Storage UI Logic Search Cache Storage UI Driver

[Extra] Sandwich Integration Logic Search Cache Storage UI Logic Search Cache Storage UI Search Driver

[Extra] Big bang Integration Logic Search Cache Storage UI

[extra] Boom!

Incremental ( top-down, bottom-up, sandwich ) NOT big bang

Integrate early, frequently, Incrementally

RCS Remote repo

RCS Remote repo

RCS Remote repo Centralized CVS Subversion

RCS Remote repo Centralized Distributed CVS SVN Hg Git Bazaar Remote repos

RCS Remote repo Centralized Distributed CVS SVN Hg Git Bazzar Remote repos

Google Code repo C:\CityConnect>hg push pushing to searching for changes http authorization required realm: Google Code hg Repository user: john password: remote: Success. C:\CityConnect> push John init

Google Code repo C:\>hg clone CityConnect requesting all changes adding changesets adding manifests adding file changes added 2 changesets with 6 changes to 6 files updating to branch default 5 files updated, 0 files merged, 0 files removed, 0 files unresolved. C:\> push JohnJean clone init

Google Code repo C:\CityConnect>hg commit -m "added add feature" push JohnJean clone init

Google Code repo C:\CityConnect>hg commit -m "added add feature" C:\CityConnect>hg push push JohnJean clone init

Google Code repo C:\CityConnect> hg pull pulling from searching for changes adding changesets adding manifests adding file changes added 1 changesets with 1 changes to 1 files (run 'hg update' to get a working copy) push John pull init

Google Code repo C:\CityConnect> hg pull pulling from searching for changes adding changesets adding manifests adding file changes added 1 changesets with 1 changes to 1 files (run 'hg update' to get a working copy) C:\CityConnect> hg update 1 files updated, 0 files merged, 0 files removed, 0 files unresolved push John pull update init

Google Code repo push John pull update /merge init

Remote repo push pull update /merge clone commit init

Remote repo push pull update /merge clone commit init

UI MSLogic Storage History Start with a ‘walking skeleton’

UI MSLogic Storage History Start with a ‘walking skeleton’

UI MSLogic Storage History Adopt RCS gradually