Source Code Control & Bug Tracking

Size: px

Start display at page:

Download "Source Code Control & Bug Tracking"

Stewart Hodge
6 years ago
Views:

http://home.hit.no/~hansha/?page=software_development O. Widder. (2013). geek&poke.

1 O. Widder. (2013). geek&poke. Available: Source Code Control & Bug Tracking Hans-Petter Halvorsen

2 O. Widder. (2013). geek&poke. Available: 2

3 Contents Source Code Control (SCC) Revision Control Version Control Source Code Management (SCM) Bug Reporting Bug Tracking Tools 3

4 Source Code Control (SCC) Version/Revision Control Source Code Management (SCM) Hans-Petter Halvorsen, M.Sc.

6 SCC Systems SVN Concurrent Versioning System 6

7 SCC Support in Programming IDEs Android Studio Visual Studio LabVIEW 7

8 Source Code Control/Version Control What is it? A version control system keeps track of all work and all changes in a set of files (typically your code files, but also other files) Allows several developers (potentially widely separated in space and time) to collaborate All Software Developers need it!!

9 Typical SCC Features Checkout, Checkin/Commit Branching, Merging File Locking (avoid concurrent access) Label/Tag Change/Change List Conflict Revision, Iteration

10 SCC Features 1.0 Label/Tag it Checkout, Checkin/Commit Branching, Merging File Locking (avoid concurrent access) Label/Tag Change/Change List/History Conflict Braching Work with Bug Fix Bug Fix Released Work with new Release Merging 2.0 Released etc. Branching in TFS:

11 Change/Change List/History Get back old files Get overview of when the files has been changed, by who, etc, It is important that you use the Comment field every time you check in your files!!

One drawback is that sometimes you must resolve

12 Conflicts and File Merging In SCC System several people may work concurrently on the same code file. One drawback is that sometimes you must resolve conflicts before you can get, check in, or merge files. 12

14 SCC Glossary O. Widder. (2013). geek&poke. Available: Repository Checkin/Commit, Checkout File Locking Version Conflict Branching, Merging Label Fork Fork in the meaning of to divide in branches, go separate ways. In software engineering, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct piece of software. The term often implies not merely a development branch, but a split in the developer community Example: OpenOffice.org forked to LibreOffice Break the build Wikipedia. (2013). Revision Control. Available: Wikipedia. (2013). Fork (Software Development). Available: 14

15 Centralized/Client Server architecture A server stores the current version(s) of a project and its history, and clients connect to the server in order to "check out" a complete copy of the project, work on this copy and then later "check in" their changes DVCS Distibuted Version Control System With a distributed version control system, there isn t one centralized code base to pull the code from. Different branches hold different parts of the code. Git is a DVCS. Other version control systems, such as SVN and CVS, use centralized version control, meaning that only one master copy of the software is used. Peer-to-peer approach

16 Centralized/ Client Cerver architecture TFS CVS SVN (Subversion) LibreSource DVCS Git Mercurial Bazaar Monotone BitKeeper

17 Centralized/Client Server architecture Client Client Client Network Client Server Repository Repository: Source Code Database

18 Distibuted Version Control System Repository peer-to-peer peer-to-peer Repository Repository Repository Repository: Source Code Database

19 Team Foundation Server SDLC Management (SDLC Software Development Life Cycle) Software Team Collaboration Source Code Management Supports Agile, Scrum, CMMI Integrated Test Tools Bug Tracking System Automated Builds Built in Team Foundation Version Control (TSVC) + Support for Git repositories Built-in support for TFS in Visual Studio (Team Explorer) Plug-in for Eclipse (Team Explorer Everywhere) MSSCCI Provider for other IDEs like LabVIEW, etc.

20 CVS CVS - Concurrent Versions System Established Free of charge CVS uses a client server architecture: a server stores the current version(s) of a project and its history, and clients connect to the server in order to "check out" a complete copy of the project, work on this copy and then later "check in" their changes Widely supported in different IDEs (Eclipse, Xcode, )

21 SVN (Subversion) Open Source License Established in 2000 Subversion is probably the version control system with the widest adoption Many different Subversion clients are available (Tortoise SVN, Mac: Versions, Xcode (built-in support for SVN))

22 Git Has become very popular today Distributed Version Control System Initially designed and developed by Linus Torvalds (Linux Guru) (2005) Git is Free of use CVS and SVN is easier to use than Git for beginners

23 Explanation: If you track down a bug in your code and want to know when it was introduced and why, file annotation is often your best tool. It shows you what commit was the last to modify each line of any file. So, if you see that a method in your code is buggy, you can annotate the file with git blame to see when each line of the method was last edited and by whom.

24 TFVC vs. Git Team Foundation Version Control (TFVC) uses a single, centralized server repository to track and version files. Local changes are always checked in to the central server where other developers can get the latest changes. Git is a Distributed Version Control System (DVCS) that uses a local repository to track and version files. Changes are shared with other developers by pushing and pulling changes through a remote, shared repository.

25 Web-based SCC Hosting Services Visual Studio Team Services (formerly Visual Studio Online ) ( TFVC or Git GitHub ( Bitbucket ( Mercurial or Git

26 Source Code Control SCC Repositories Web-based SCC Hosting Services (Montly payment/5 users free of charge/free for open source projects) TFVC or Git Git or Mercurial Git

27 Bugtracking O. Widder. (2013). geek&poke. Available: Systems Hans-Petter Halvorsen, M.Sc.

Bugs A software bug is an error, flaw, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to

29 Bugs A software bug is an error, flaw, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways They found a bug (actually a moth) inside a computer in 1947 that made the program not behaving as expected. This was the first real bug. 29

30 Why Find Bugs early? Cost per defects Software Development Life Cycle (SDLC)

31 Bugs vs. Features It's not a bug - it's an undocumented feature J For as long as I've been a software developer and used bug tracking systems, we have struggled with the same fundamental problem in every single project we've worked on: how do you tell bugs from feature requests?

Software Releases Before the software is released Alpha Release(s) Beta Release(s) RC - Release Candidate(s) RTM Release To Manufactoring Maintenance

32 Software Releases Before the software is released Alpha Release(s) Beta Release(s) RC - Release Candidate(s) RTM Release To Manufactoring Maintenance (after the software is released) Patches (small fixes) SP - Service Packs (lots of small fixes and pathes bundle together) Start Planning next release 32

33 Example - Windows 8 Start planning and development of Windows 8, 2008/2009 (the planning started before Windows 7 was released) Internal Builds xxxx xxxx Internal Alpha versions, Alpha 1, 2, 3 Internal Builds xxxx xxxx Internal Milestone1 Release (build 7850), Internal Milestone2 (build 7955), Milestone3 (build 7989) Developer Preview (build 8102), Internal Builds xxxx xxxx Consumer Preview (build 8250), Internal Builds xxxx xxxx Release Preview (build 8400), Internal Builds xxxx xxxx RTM Release (build 9200), major.minor.maintenance.build It is normal to build the software automatically every night, ready for internal tester the day after

34 Bug Tracking Systems Team Foundation Server/ Visual Studio Team Services Jira Bugzilla Clearquest

35 Team Foundation Server You Add Bugs as Work Items 35

36 Summary All Software Developers need to use a SCC system All Software Developers need to use a Bug Tracking system

References I. Sommerville, Software Engineering: Pearson, 2010. Wikipedia. (2013). Revision Control. Available: http://en.wikipedia.org/wiki/source_code_management Wikipedia. (2013). Fork (Software Development).

37 References I. Sommerville, Software Engineering: Pearson, Wikipedia. (2013). Revision Control. Available: Wikipedia. (2013). Fork (Software Development). Available: S. Adams. Dilbert. Available: O. Widder. (2013). geek&poke. Available: B. Lund. (2013). Lunch. Available: Comparison of Revision Control Software. Available: Wikipedia. (2013). Distributed Revision Control. Available: Wikipedia. (2013). Software Versioning. Available: 7 Version Control Systems Reviewed:

Hans-Petter Halvorsen, M.Sc. University College of Southeast Norway www.

38 Hans-Petter Halvorsen, M.Sc. University College of Southeast Norway Blog:

Source Code Control. Quiz with Explainations. Hans-Petter Halvorsen, M.Sc.

Source Code Control. Quiz with Explainations. Hans-Petter Halvorsen, M.Sc. Source Code Control Quiz with Explainations Hans-Petter Halvorsen, M.Sc. Questions 1. What is SCC? 2. List at least 5 different SSC Systems 3. Why do we need a SCC/Version Control System? 4. What is Distributed