DOCSLIB.ORG

Distributed Version Control Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Distributed Version Control Systems Distributed Version Control Systems Dipl. Medieninformatiker (BA) Daniel Kuhn Master degree course Computer Science and Media Hochschule der Medien Nobelstrasse 10, 70569 Stuttgart e-mail: [email protected] July 2010 Abstract integrity checks. Both SCCS and RCS are Version Control Systems that use a locking mechanism to lock files for other Traditional centralized Version Control Systems (VCS) as users when they are edited. e.g. CVS and SVN, which were used since the 1980’s in al- 1989 the more familiar Concurrent Versions System most every company, are facing competition by a new ap- (CVS) was developed as an improvement of RCS. CVS proach to source code management. Distributed Version showed many additions like the support for multiple files Control Systems like Bazaar, Darcs, Mecurial and Git are and the support for multiple users. But the major advantage changing the way repositories are stored and distributed by of CVS was support for merging concurrently changed files representing a new and more contemporary mindset. Today instead of using a locking mechanism. This enabled devel- Distributed Version Control Systems have therefore become opers to work collaboratively on their projects. But CVS very popular in the open-source community with many de- had some restrictions concerning the handling of directo- velopers using them. ries and binary-files. With the growth of the internet, users This paper aims to show the requirements, advantages of CVS criticized the lack of supporting a native remote ac- and disadvantages of Distributed Version Control Systems cess in CVS and demanded for a solution. So in 1994 a and discusses the differences to Centralized Version Control group of developers implemented an extension to use CVS Systems us the software Git as an example. The document over TCP, which was a large improvement to CVS, which shows and explains the functionality of the system and takes could now be used easier over the internet. a look under the hood by not focusing on the use of the tool, Later in the year 2000 a company called CollabNet de- but by rather analyzing how the tool handles its tasks. cided to develop a replacement system for CVS. So Ben Collins-Sussman, Brian Behlendorf and Jason Robbins of 1. Introduction CollabNet started the Subversion (SVN) Project. The sub- version CVS is still being used today and considered an in- Since the 1970’s Version Control Systems have been used dustry standard. Subversion is an Open-Source Software to archive and manage different versions of files, especially in accordance with the Debian Free Software Guidelines source code. Version Control started in 1972 with the re- (DFSG)1. Subversion brought many advantages to develop- lease of the first system called Source Code Control Sys- ers like better file-handling, including a directory structure, tem (SCCS). SCCS was developed to manage source code, which lead to more focus to the project instead of only files. configuration-files or documentations and focused on man- SVN has real atom commits ensuring consistency, better aging single files and single users. SCCS has brought fea- branching and tagging and an abstract repository interface tures like: letting developers keep track of the history of a for an easy development of different access methods. [5] file, using checksums to detect data corruption, using a for- As of today, Centralized Version Control Systems - es- ward delta system and providing support for binary files [3] pecially Subversion - are the top-dogs in companies. With [4]. Bitkeeper, developed in 1997, there was another approach Another early version control system is the Revision to source control management: Distributed Version Con- Control System (RCS), developed in the 1980’s. Just like trol Systems. These systems have become more and more SCCS, RCS is a file-based, single-user oriented version popular with the development of Git, Mercurial, Bazaar and control software that simply stores different versions of files Darcs. in the file-system. But unlike SCCS, RCS keeps no track of the history of a file and does not provide checksums for 1http://www.debian.org/social_contract#guidelines 1 Git is a Distributed Version Control System (DVCS) in tween nodes over distances. When it comes to data storage development since 2005 as an open-source project started and delivery one has to think about general questions like by Linus Torvalds. The Git project was started with the in- 1. Security – is my data safe? tention of replacing the proprietary Bitkeeper DVCS used to maintain the linux kernel and free to use for open-source 2. Performance – can I deliver the data quickly? projects. After the Bitkeeper developers decided to change their licensing policy Linus Torvalds project leader of the 3. Reliability and Availibility – can the data be accessed linux kernel, started looking for an appropriate replacement, 24/7 without downtime? which he ultimatly couldn’t find. Therefore Torvalds de- 4. Consistency – is my system state consistent over every cided to design the Git DVCS to meet the needs of the ker- node? nel and its developers. 5. Maintenance – can I maintain my infrastructure easily? 2. Polymorphism of Version Control These five points are the general requirements of a ver- Systems sion control system. However some of these requirements are orthogonal to each other. A system which is performing One of the easiest “versioning systems” is local and man- well, highly secure, highly reliable, easy to maintain and ual versioning. Everybody has used it, maybe without even always has a consistent system state is hardly possible to thinking about it as a kind of version control. Local or design without spending a tremendous amount of money. manual versioning means to make a copy of a document Fact is, if you use a centralized system, it is easy to and save it under a different name (e.g. myImportantLet- backup the data and maintain the servers and storage sys- ter_20100202). This version control system does neither tems. But when it comes to scalability and distribution, cen- perform well, nor is it efficient or safe in any way. But it is tralized systems will not perform well – which can also lead easy to use and understand and may fit personal versioning. to general failures. On top of that there is always the risk of However when it comes to a professional level a better ver- a single point of failure. sion control system is needed. So it becomes quite obvious The same questions arise when comparing CVCS with that version control can be done in many ways and should DVCS. A centralized system will always be easier to main- always fit the use cases by fulfilling its requirements. tain. Servers are mostly in one place and contain many One of the common purposes of Version Control Sys- repositories for multiple projects. This makes it easy to tems is to enable groups of people to work together on (any backup the whole data in comparison to a distributed sys- kind of) files. They can change, archive, merge, branch or tem. DVCS are taking another approach on the backup as- synchronize files of which the system keeps a history. An- pect and consistency. The idea is that if you clone a reposi- other purpose is archiving and backupping. Content in the tory to your local drive, it contains all the history (including system should possibly be safe and free of data-loss. Com- branches and merges) from that one developer who’s repos- bining the two aspects of collaboration and security leads to itory was cloned. But you never see the code of all devel- Centralized Version Control Systems (CVCS). Traditional opers working on the same project. A developer can imple- systems like CVS and more common SVN are centralized, ment a feature and say “hey I’ve got the feature ready, pull containing only one main repository per project usable by the code if you like” – and if a developer likes to pull that every member of the group. CVCS are used in most of feature, he does and merges the code right into his reposi- the companies and therefore have reached their maturity by tory. So there is not just a single development version, like being considered an industry-standard. Aside from CVCS one might be used from CVCS, but rather multiple versions there is another approach to achieve version control in a of the code. The result being nobody knows the whole sys- slightly different way. Distributed Version Control Sys- tem state. This approach to development involves a change tems like Bazaar, Darcs, Mercurial and Git use decentral- of the mindset used in the traditional centralized systems, ized repositories for versioning data which is spread among because Distributed Version Control Systems focus not on users. backup, but rather on easy versioning and the sharing of fea- tures to a program instead of having only the one version. 2.1 A quick comparison between centralized Linus Torvalds (in Google tech talk [7]) sees the fact that and decentralized VCS everybody pulls from everybody as an advantage, because your code is distributed and backuped by other developers First I’d like to give a more general view of centralization and you don’t have to care about it. But I disagree. This may and decentralization. Comparing the systems most of the work for famous developers like Mr. Torvalds, but perhaps time leads to the same problems. Not only for Version Con- not for the “nooby-open-source-project-contributer”. But trol Systems, but for almost every system sharing data be- even if everybody pulls your code, this involves only the 2 code of a feature that you released and not your code you therefore the need to combine and motivate more develop- are working on in your development branch (which is only ers to contribute to their project.
Load more

Recommended publications
  • Efficient Algorithms for Comparing, Storing, and Sharing
    EFFICIENT ALGORITHMS FOR COMPARING, STORING, AND SHARING LARGE COLLECTIONS OF EVOLUTIONARY TREES A Dissertation by SUZANNE JUDE MATTHEWS Submitted to the Office of Graduate Studies of Texas A&M University in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY May 2012 Major Subject: Computer Science EFFICIENT ALGORITHMS FOR COMPARING, STORING, AND SHARING LARGE COLLECTIONS OF EVOLUTIONARY TREES A Dissertation by SUZANNE JUDE MATTHEWS Submitted to the Office of Graduate Studies of Texas A&M University in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY Approved by: Chair of Committee, Tiffani L. Williams Committee Members, Nancy M. Amato Jennifer L. Welch James B. Woolley Head of Department, Hank W. Walker May 2012 Major Subject: Computer Science iii ABSTRACT Efficient Algorithms for Comparing, Storing, and Sharing Large Collections of Evolutionary Trees. (May 2012) Suzanne Jude Matthews, B.S.; M.S., Rensselaer Polytechnic Institute Chair of Advisory Committee: Dr. Tiffani L. Williams Evolutionary relationships between a group of organisms are commonly summarized in a phylogenetic (or evolutionary) tree. The goal of phylogenetic inference is to infer the best tree structure that represents the relationships between a group of organisms, given a set of observations (e.g. molecular sequences). However, popular heuristics for inferring phylogenies output tens to hundreds of thousands of equally weighted candidate trees. Biologists summarize these trees into a single structure called the consensus tree. The central assumption is that the information discarded has less value than the information retained. But, what if this assumption is not true? In this dissertation, we demonstrate the value of retaining and studying tree collections.
    [Show full text]
  • Higher Inductive Types (Hits) Are a New Type Former!
    Git as a HIT Dan Licata Wesleyan University 1 1 Darcs Git as a HIT Dan Licata Wesleyan University 1 1 HITs 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! They were originally invented[Lumsdaine,Shulman,…] to model basic spaces (circle, spheres, the torus, …) and constructions in homotopy theory 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! They were originally invented[Lumsdaine,Shulman,…] to model basic spaces (circle, spheres, the torus, …) and constructions in homotopy theory But they have many other applications, including some programming ones! 2 Generator for 2 equality of equality Patches Patch a a 2c2 diff b d = < b c c --- > d 3 3 id a a b b
    [Show full text]
  • DVCS Or a New Way to Use Version Control Systems for Freebsd
    Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions DVCS or a new way to use Version Control Systems for FreeBSD Ollivier ROBERT <[email protected]> BSDCan 2006 Ottawa, Canada May, 12-13th, 2006 Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions Agenda 1 Brief history of VCS 2 FreeBSD context & gures 3 Is Arch/baz suited for FreeBSD? 4 Mercurial to the rescue 5 New processes & policies needed 6 Conclusions Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions The ancestors: SCCS, RCS File-oriented Use a subdirectory to store deltas and metadata Use lock-based architecture Support shared developments through NFS (fragile) SCCS is proprietary (System V), RCS is Open Source a SCCS clone exists: CSSC You can have a central repository with symlinks (RCS) Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions CVS, the de facto VCS for the free world Initially written as shell wrappers over RCS then rewritten in C Centralised server Easy UI Use sandboxes to avoid locking Simple 3-way merges Can be replicated through CVSup or even rsync Extensive documentation (papers, websites, books) Free software and used everywhere (SourceForge for example) Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions CVS annoyances and aws BUT..
    [Show full text]
  • Darcs 2.0.0 (2.0.0 (+ 75 Patches)) Darcs
    Darcs 2.0.0 (2.0.0 (+ 75 patches)) Darcs David Roundy April 23, 2008 2 Contents 1 Introduction 7 1.1 Features . 9 1.2 Switching from CVS . 11 1.3 Switching from arch . 12 2 Building darcs 15 2.1 Prerequisites . 15 2.2 Building on Mac OS X . 16 2.3 Building on Microsoft Windows . 16 2.4 Building from tarball . 16 2.5 Building darcs from the repository . 17 2.6 Building darcs with git . 18 2.7 Submitting patches to darcs . 18 3 Getting started 19 3.1 Creating your repository . 19 3.2 Making changes . 20 3.3 Making your repository visible to others . 20 3.4 Getting changes made to another repository . 21 3.5 Moving patches from one repository to another . 21 3.5.1 All pulls . 21 3.5.2 Send and apply manually . 21 3.5.3 Push . 22 3.5.4 Push —apply-as . 22 3.5.5 Sending signed patches by email . 23 3.6 Reducing disk space usage . 26 3.6.1 Linking between repositories . 26 3.6.2 Alternate formats for the pristine tree . 26 4 Configuring darcs 29 4.1 prefs . 29 4.2 Environment variables . 32 4.3 General-purpose variables . 33 4.4 Remote repositories . 34 3 4 CONTENTS 4.5 Highlighted output . 36 4.6 Character escaping and non-ASCII character encodings . 36 5 Best practices 39 5.1 Introduction . 39 5.2 Creating patches . 39 5.2.1 Changes . 40 5.2.2 Keeping or discarding changes . 40 5.2.3 Unrecording changes .
    [Show full text]
  • Distributed Versioning for Everyone
    Distributed versioning for everyone Distributed versioning for everyone Nicolas Pouillard [email protected] March 20, 2008 Nicolas Pouillard Distributed versioning for everyoneMarch 20, 2008 1 / 48 Distributed versioning for everyone Introduction Outline 1 Introduction 2 Principles of Distributed Versioning 3 Darcs is one of them 4 Conclusion Nicolas Pouillard Distributed versioning for everyoneMarch 20, 2008 2 / 48 Distributed versioning for everyone Introduction SCM: “Source Code Manager” Keeps track of changes to source code so you can track down bugs and work collaboratively. Most famous example: CVS Numerous acronyms: RCS, SCM, VCS DSCM: Distributed Source Code Manager Nicolas Pouillard Distributed versioning for everyoneMarch 20, 2008 3 / 48 Distributed versioning for everyone Introduction Purpose What’s the purpose of this presentation Show the importance of the distributed feature Enrich your toolbox with a DSCM Exorcize rumors about darcs Show how DSCM are adapted for personal use What’s not the purpose of it A flame against other DSCMs A precise darcs tutorial A real explanation of the Theory of patches Nicolas Pouillard Distributed versioning for everyoneMarch 20, 2008 4 / 48 Distributed versioning for everyone Principles of Distributed Versioning Outline 1 Introduction 2 Principles of Distributed Versioning 3 Darcs is one of them 4 Conclusion Nicolas Pouillard Distributed versioning for everyoneMarch 20, 2008 5 / 48 Distributed versioning for everyone Principles of Distributed Versioning Distributed rather than centralized
    [Show full text]
  • Version Control
    Génie Logiciel Avancé Cours 7 — Version Control Stefano Zacchiroli [email protected] Laboratoire PPS, Université Paris Diderot - Paris 7 5 mai 2011 URL http://upsilon.cc/zack/teaching/1011/gla/ Copyright © 2011 Stefano Zacchiroli License Creative Commons Attribution-ShareAlike 3.0 Unported License http://creativecommons.org/licenses/by-sa/3.0/ Stefano Zacchiroli (Paris 7) Version Control 5 mai 2011 1 / 58 Disclaimer slides in English interactive demos Stefano Zacchiroli (Paris 7) Version Control 5 mai 2011 2 / 58 Sommaire 1 Version control Configuration management diff & patch Version control concepts Brief history of version control systems 2 Revision Control System (RCS) 3 Concurrent Versions System (CVS) 4 Subversion 5 Git 6 References Stefano Zacchiroli (Paris 7) Version Control 5 mai 2011 3 / 58 Sommaire 1 Version control Configuration management diff & patch Version control concepts Brief history of version control systems 2 Revision Control System (RCS) 3 Concurrent Versions System (CVS) 4 Subversion 5 Git 6 References Stefano Zacchiroli (Paris 7) Version Control 5 mai 2011 4 / 58 Sommaire 1 Version control Configuration management diff & patch Version control concepts Brief history of version control systems 2 Revision Control System (RCS) 3 Concurrent Versions System (CVS) 4 Subversion 5 Git 6 References Stefano Zacchiroli (Paris 7) Version Control 5 mai 2011 5 / 58 Change During the life time of a software project, everything changes : bugs are discovered and have to be fixed (code) system requirements change and need to be implemented external dependencies (e.g. new version of hardware and software you depend upon) change competitors might catch up most software systems can be thought of as a set of evolving versions potentially, each of them has to be maintained concurrently with the others Stefano Zacchiroli (Paris 7) Version Control 5 mai 2011 6 / 58 Configuration management Definition (Configuration Management) Configuration Management (CM) is concerned with the policies, processes, and tools for managing changing software systems.
    [Show full text]
  • Continuous Integration for Decentralised Development of Service-Based Software Systems
    Continuous Integration for Decentralised Development of Service-Based Software Systems by Jameel Almalki Thesis Submitted to Flinders University for the degree of Doctor of Philosophy College of Science and Engineering 9th August 2018 Declaration I certify that this thesis does not include any prior material submitted for a degree or diploma in any university without acknowledgment; and to the best of my knowledge and belief it does not include any prior material published or written by another individual with the exception of where due reference is used in the text. Jameel Almalki July 30th, 2018 2 Acknowledgements Firstly and most importantly, I want to thank Allah Almighty for giving me blessings, opportunities, strength and guidance to endure this challenging task to the end. My unreserved appreciation and gratitude go to my parents and my brothers and sisters for their continuous support, prayers and encouragement, which gave me the strength to succeed in my PhD research journey. May Allah bless you all. My greatest indebtedness is to my wife, Hamdah, for her endless love, support, patience and sacrifice while I have been consumed with this research in recent years. My thanks and love are also extended to my two precious daughters, Diala and Ladan, and my son, Elias, for all the joy and love in my life. Thank you very much, you are indeed my treasures. I also would like to express my deepest gratitude and appreciation to my supervisor, Dr. Haifeng Shen, for his enthusiastic support, insightful suggestions and valuable guidance throughout this research. Certainly, without his encouragement, invaluable knowledge and support this work would never have been completed.
    [Show full text]
  • David's Advanced Revision Control System
    Hazırlık Darcs Hakkında Pratik Okuma Odevi¨ David’s Advanced Revision Control System Can Burak C¸ilingir1 1Istanbul˙ Bilgi Universitesi¨ Bilgisayar Bilimleri B¨ol¨um¨u [email protected] 5 S¸ubat 2007 Can Burak C¸ilingir Darcs Hazırlık Darcs Hakkında Versiyon Y¨onetimi Pratik Ge¸cmi¸s Okuma Odevi¨ Ne zaman bitecek? 1 Hazırlık Versiyon Y¨onetimi Ge¸cmi¸s 2 Darcs Hakkında 3 Pratik 4 Okuma Odevi¨ Can Burak C¸ilingir Darcs Hazırlık Darcs Hakkında Versiyon Y¨onetimi Pratik Ge¸cmi¸s Okuma Odevi¨ neye yarar? Can Burak C¸ilingir Darcs Hazırlık Darcs Hakkında Versiyon Y¨onetimi Pratik Ge¸cmi¸s Okuma Odevi¨ Aegis, ArX, Arch, BitKeeper, CM Synergy, CVS, Code Co-Op, Codeville, IBM Rational ClearCase, Mercurial, Monotone, OpenCM Perforce, PureCM, RCS, Subversion, Superversion, Vesta, Visual SourceSafe, bazaar-ng, git, monotone, svk http://better-scm.berlios.de/comparison/ http://zooko.com/revision control quick ref.html Can Burak C¸ilingir Darcs Hazırlık Darcs Hakkında Versiyon Y¨onetimi Pratik Ge¸cmi¸s Okuma Odevi¨ Aegis, ArX, Arch, BitKeeper, CM Synergy, CVS, Code Co-Op, Codeville, IBM Rational ClearCase, Mercurial, Monotone, OpenCM Perforce, PureCM, RCS, Subversion, Superversion, Vesta, Visual SourceSafe, bazaar-ng, git, monotone, svk http://better-scm.berlios.de/comparison/ http://zooko.com/revision control quick ref.html Can Burak C¸ilingir Darcs Hazırlık Darcs Hakkında Versiyon Y¨onetimi Pratik Ge¸cmi¸s Okuma Odevi¨ rcs Revision Control System, tek ki¸si cvs Concurrent Versioning System, birden fazla ki¸si svn Subversion, daha d¨uzg¨un
    [Show full text]
  • Esa Study Contract Report
    ESA STUDY CONTRACT REPORT ESA Contract No: Subject: Contractor: ESA ITT Number Current and Future Tech- Distributed Systems Group, AO/3-12280/07/NL/CB nologies for Collaborative Vienna University of Tech- Working Environments nology ESA CR() No: No of volumes: 1 Contractor’s Reference: This Volume No: 1 TEUN Abstract: This document reports the final, detailed result of the study on current and future technologies for collaborative working environments (CWEs). The goal of this study is to analyze current CWEs and whether they and their future trends are suitable for large- scale multinational organizations. To this end, we have analyzed the structure of large-scale organizations in general, and of ESA in particular, with respect to organization, geographical distribution, and IT environments. Requirements for CWEs used in collaborative work are presented. Based on an initial list of criteria given by ESA, we have revised and extended the list to introduce a comprehensive set of criteria for evaluating CWEs. The state-of-the- art CWEs are discussed and classified. We have selected 15 representative CWE products and evaluated and compared them in detail. From the evaluation and comparison of CWE products, we have presented our findings of current issues and future trends of CWEs. In particular, existing products provide many features required by large-scale and multinational organizations but those features are not well-integrated into a single system. Due to the complexity of collaborative work within those organizations, often many CWEs are used in parallel and it is not easy to integrate those CWEs together. The work described in this report was done under ESA Contract.
    [Show full text]
  • Version Control with Git Why Using Version Control?
    Version control with Git Why using version control? • Backup • Easy experimentation with parallel branches • Collaboration across teams • e.g. All of Google’s code lies in one repository • Formal software development process • Tagging of releases • Continuous integration • Pull requests, code reviews Duckietown 2 History of (non-proprietary) version control systems • 1970s: Print everything out. Duckietown 3 History of (non-proprietary) version control systems • 1990s: CVS • Independent history for each single ile. • 2000: Subversion • Client-server architecture. • Repository snapshots, introductions of branches. • 2005: Distributed Version Control (Git, Mercurial, Darcs, Bazaar, …) • Peer-to-peer network of replicated copies. • 2010s: Services on top (Github, Gitlab, …) • Issue tracking, pull requests, continuous integration, … Duckietown 4 Git • Created by Linus Torvalds (1969-, Finnish), author of Linux • Created for Linux kernel development Duckietown 5 Git • Created by Linus Torvalds (1969-, Finnish), author of Linux • Created for Linux kernel development When asked why [Linus Torvalds] called the new software, "git," British slang meaning "a rotten person," he said: “I'm an egotistical bastard, so I name all my projects after myself. First Linux, now git." source Duckietown 6 Jedi knights build their own lightsabers Duckietown 7 A roboticist’s output is typically limited by tools • Learn to use the tools that you have. • Modify the tools to it your needs. • Create new tools. • Learn enough to be able to create the tools that you need. Duckietown 8 Commit graph Duckietown 9 Commit graph master Duckietown 10 Duckietown 11 Git explained with dynamical systems Dynamical system Version control / “patch theory” state Commit graph command transition Patches function hash function (pretend injective) Duckietown 12 “Git Flow” branching model • Git does not impose any semantics on the branches.
    [Show full text]
  • Bill Laboon Friendly Introduction Version Control: a Brief History
    Git and GitHub: A Bill Laboon Friendly Introduction Version Control: A Brief History ❖ In the old days, you could make a copy of your code at a certain point, and release it ❖ You could then continue working on your code, adding features, fixing bugs, etc. ❖ But this had several problems! VERSION 1 VERSION 2 Version Control: A Brief History ❖ Working with others was difficult - if you both modified the same file, it could be very difficult to fix! ❖ Reviewing changes from “Release n” to “Release n + 1” could be very time-consuming, if not impossible ❖ Modifying code locally meant that a crash could take out much of your work Version Control: A Brief History ❖ So now we have version control - a way to manage our source code in a regular way. ❖ We can tag releases without making a copy ❖ We can have numerous “save points” in case our modifications need to be unwound ❖ We can easily distribute our code across multiple machines ❖ We can easily merge work from different people to the same codebase Version Control ❖ There are many kinds of version control out there: ❖ BitKeeper, Perforce, Subversion, Visual SourceSafe, Mercurial, IBM ClearCase, AccuRev, AutoDesk Vault, Team Concert, Vesta, CVSNT, OpenCVS, Aegis, ArX, Darcs, Fossil, GNU Arch, BitKeeper, Code Co-Op, Plastic, StarTeam, MKS Integrity, Team Foundation Server, PVCS, DCVS, StarTeam, Veracity, Razor, Sun TeamWare, Code Co-Op, SVK, Fossil, Codeville, Bazaar…. ❖ But we will discuss git and its most popular repository hosting service, GitHub What is git? ❖ Developed by Linus Torvalds ❖ Strong support for distributed development ❖ Very fast ❖ Very efficient ❖ Very resistant against data corruption ❖ Makes branching and merging easy ❖ Can run over various protocols Git and GitHub ❖ git != GitHub ❖ git is the software itself - GitHub is just a place to store it, and some web-based tools to help with development.
    [Show full text]
  • Anatomy of the Deployment Pipeline
    Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The authors and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The publisher offers excellent discounts on this book when ordered in quantity for bulk purchases or special sales, which may include electronic versions and/or custom covers and content particular to your business, training goals, marketing focus, and branding interests. For more information, please contact: U.S. Corporate and Government Sales (800) 382–3419 [email protected] For sales outside the United States please contact: International Sales [email protected] Visit us on the Web: informit.com/aw Library of Congress Cataloging-in-Publication Data: Humble, Jez. Continuous delivery : reliable software releases through build, test, and deployment automation / Jez Humble, David Farley. p. cm. Includes bibliographical references and index. ISBN 978-0-321-60191-9 (hardback : alk. paper) 1. Computer software--Development. 2. Computer software--Reliability. 3. Computer software--Testing. I. Farley, David, 1959- II. Title. QA76.76.D47H843 2010 005.1--dc22 2010022186 Copyright © 2011 Pearson Education, Inc. All rights reserved. Printed in the United States of America.
    [Show full text]