Software configuration management

Size: px

Start display at page:

Download "Software configuration management"

Brianna Berry
5 years ago
Views:

1 Software Engineering Theory Software configuration management Lena Buffoni/ Kristian Sandahl Department of Computer and Information Science

2 2 Maintenance Requirements System Design (Architecture, High-level Design) Validate Requirements, Verify Specification Verify System Design Acceptance Test (Release testing) System Testing (Integration testing of modules) Module Design (Program Design, Detailed Design) Verify Module Design Verify Implementation Module Testing (Integration testing of units) Implementation of Units (classes, procedures, functions) Unit testing Project Management, Software Quality Assurance (SQA), Supporting Tools, Education

3 What is configuration management? 3 Configuration Item Identification Source code modules Test scripts Design documents Build systems SCM

4 What is configuration management? 4 File A v.03 File C v.3.3 File B v0.1 Change File A v.03 File C v.3.4 File B v0.1 Change File A v.03 File C v.3.3 File B v0.11 Baseline - a "snap-shot" of configuration items. Known to work together. Normally reviews in some way. For example a release. How do we control changes?

Project: Classification: Priority: Date:

5 5 What is configuration management? Configuration Item Identification Source code modules Test scripts Design documents Build systems CHANGE REQUEST Project: Classification: Priority: Date: Change Description: SCM Change Control Board (CCB) Make change decisions. Only large changes (e.g. new major requirements) Configuration control Only authorized people may make changes Larger changes - change requests

6 6 What is configuration management? Configuration Item Identification Source code modules Test scripts Design documents Build systems Auditing Ensure that the items are complete and consistent. Make sure that the configuration is tested and meets requirements. SCM Configuration control Larger changes - change requests Status accounting Document and report changes to those involved.

7 SCM tools 7 Change Management Workflow systems Define processes for change requests Change report system Bug-tracking New features Change request (e.g free alternatives: Bugzilla, Trac) What is a bug / what is a feature? Tool examples: Clear Case, Visual Source safe Perforce, CVS Subversion Git Revision Control Systems

8 8 Zip and 6. Sends a zip file with code Nahid BAD IDEA 1.Creates GUI module 5. Updates GUI module 8. Sends a zip file with code Daniel 7. Solves a bug in the DBMS Anna 2. Sends a zip file with code 4. Sends a zip file with code Mohamed C RELEASE!! 3. Creates DBMS module

9 File Server Sharing 9 5. Mohamed uploads the file 4. Anna uploads the file FILE A RG File Server 1. Anna and Mohamed copy file A from server ALSO, A BAD IDEA 2. Anna edits the file FILE A GR 6. Both synchronize, i.e. they copy the files from server FILE A G 3. Mohamed edits the file (independently) Anna Mohamed Anna s change is lost in space

10 SCM: Lock-Modify-Unlock 10 A BETTER IDEA, but 4. Anna uploads the file, and unlocks 2. Anna locks the file, only she can modify FILE A R SCM Repository 1. Anna and Mohamed copy file A from server Rigid, developers cannot work on the same file False sense of security. Can modify two dependent files Ex. Microsoft Visual SourceSafe 5. Mohamed locks the file 3. Anna edits the file FILE A R FILE A G 6. Mohamed edits the file Anna Mohamed

11 SCM: Centralized modify-merge 11 Pretty good YR FILE A SCM Repository Example CVS, Perforce, Subversion 8. Mohamed commits his change. 4. Anna commits the changes to the repository 1. Anna and Mohamed copy file A from server. 5. Mohamed makes an update (also called sync) 2. Anna edits the file FILE A Anna R This is called Check-out. 7. Mohamed resolves the conflict. FILE A GY Mohamed 3. Mohamed edits the file 6. The system tries to merge the files, but we have a conflict.

12 SCM: Decentralized modify-merge 12 Pretty good 8. Anna pulls (fetches and merges) down the new changes to her repository. 2. Anna changes and commits to the local repository and pushes them to the public repository FILE A Anna FILE A Public Repository 1. Anna and Mohamed clone the public repository to local repositories. 3. Mohamed pulls the latest version and rebases his changes on top For example Git (quite new, used by e.g. Linux kernel) FILE A Mohamed 5. Mohamed pushes the changes to the public repository. 4. Mohamed makes some more changes and commits (locally).

13 SCM: Decentralized forked repositories 13 Anna s public repository, the official repository 1. Mohamed forks the public repository Mohamed s public repository 6. Anna reviews Mohamed's changes and pulls them into her repository Public Repository 2. Anna Mohamed clone their public repositories to local repositories. 5. Mohamed makes a pull request to Anna s repository 4. Mohamed pushes the changes to the public repository. Anna Mohamed 3. Mohamed makes some more changes and commits (locally).

14 14 History Tree Test Development Branch(es) v v Commit Merge Trunk v v v v Release Branch(es) or tags v1.2.24

How do we know that integration is correct?

15 Integration Problem 15 Developer Developer Developer Independent work during weeks How do we integrate? How do we know that integration is correct? Continuous integration Integrate frequently ( Daily ) Important practices: Automated build Automated Test Use of SCM systems

16 Continuous Integration - Workflow 16 1.Checkout 2. Coding and new tests SCM Repository 8. Update 4. Update 7. Commit Build and Integration Server 9. Automatic Build, Test, Integration 10. Report Web, etc. 3. Automated build and test locally 5. Resolve conflicts 6. Automated build and test locally

17 17 Commit and build strategy On commit builds vs. periodic builds Push vs. pull requests, code review Test the changes before you commit to the trunk Commit messages

18 18 Guidelines Automation means that a build must be easy to trigger Continuous integration goes hand in hand with version control Be careful of what you put in the trunk

Automation 19 Automated Build Update from SCM (if server)

g. Doxygen) Daily build, SCM triggered etc.

system tests Performs automatic regression testing Smoke

processes) Typically just the integration server Create

19 Automation 19 Automated Build Update from SCM (if server) Compile code (make, Maven etc.) Generate documentation (e.g. Doxygen) Daily build, SCM triggered etc. Automated Test Run test suite (Unit tests) Automated system tests Performs automatic regression testing Smoke testing can be used Automated Integration (post processes) Typically just the integration server Create deployment packages (msi, RPM etc.) Automated tags in SCM Automated version numbering

20 20 CI tools tools that make continuous integration easier and more efficient support for version control build/test software projects continuously monitor externally run jobs customizable and extensible Hudson/Jenkins, GitLab tools

21 21 A tool does not continuous integration make! Continuous integration is a process Commit regularly Define a commit strategy Keep the trunk stable Maintain the test-suite

22 The end. Thank you! Questions?

February 2 nd Jean Parpaillon

February 2 nd Jean Parpaillon Using GIT with Kerrighed project Kerrighed Summit '07 February 2 nd 2007 Jean Parpaillon Table of contents Kerrighed SCM Subversion GIT GIT with Kerrighed References 2 Kerrighed