ALM: Continuous Integration. José Almeida, Microsoft

Transcription

1 ALM: Continuous Integration José Almeida, Microsoft

2 Agenda Issues Addressed Getting Started What is CI? CI Practices

3 About Continuous Integration

4 What is Continuous Integration? CI is the thread that ties development practices together

5 What is Continuous Integration? It s a software development pratice Team members integrate frequently Each integration is fully automated and verifiable GOAL: Find errors as quickly as possible And fix them as quickly as possible

6 The CI Cycle Publish results Monitor Repository Validate product Automation Get latest changes Build product

7 How Does CI Help SW Development?

8 How Does It Help? By leveraging other development best practices: Correct source code management Self-validating code Adherence to coding standards

9 Common Issues in SW Development Dependency issues Code was built on a developer s machine without the latest version of it s dependencies

10 Common Issues in SW Development Dependency issues Code traceability It s difficult to track the code that corresponds to the binary currently deployed in the production environment

11 Common Issues in SW Development Dependency issues Regressions Code traceability A commit causes an error in a previously working functionality

12 Common Issues in SW Development Dependency issues Regressions Code traceability Low coverage All our tests pass but we re still finding lots of defects!

13 Common Issues in SW Development Dependency issues Regressions Adherence to best-practices We found some issues with the version of the code currently in production and it turns out they re documented best practices. Code traceability Low coverage

14 CI Practices

15 CI Practice Maintain a Single Source Repository Automate the Build Make Your Build Self-Testing Everyone Commits Every Day Every Commit Should Build the Mainline on an Integration Machine Keep the Build Fast Test in a Clone of the Production Environment Make it Easy For Anyone To Get The Latest Executable Everyone Can See What s Happening Automate Deployment Martin Fowler, Continuous Integration

16 The Repository Single repository for all artifacts Code Scripts DB schemas Install scripts Basic rule of thumb: Get a clean machine, plug it to the network, download the latest sources and build the product

17 The Build Requires a degree of automation VS project files are MSBuild scripts Team Build wraps all project build scripts within a master script file Advantages: Reduce/eliminate repetitive, manual and error-prone tasks Free people for value-added tasks Increase integration frequency

18 Self-Validating Code Unit Tests: Test specific aspects of a functionality Execute rapidly Independent of each other Independent of the surrounding environment Independent of execution order Automated Ideal to be integrated into an automated Build

19 Self-Validating Code Make your code self-validating by writing Unit Tests

20 Self-Validating Code Don t have the time?

21 Self-Validating Code Do you write a console or winforms app that calls your methods? That s a unit test! Place that code in a method decorated with the [TestMethod] attribute in a test project

22 Getting Started

23 Getting Started With CI Decide to add CI to your product development Establish a consistent use of a single source repository Setup your CI platform Add other practices to your product development (unit testing, code analysis, etc.)

24 Summing Up

25 Continuous Improvement Quality improvement Automate integration tasks Fewer errors CI Reduce integration time Continuous Improvement Integrate more often

26 Conclusion CI is not only about integrating source code...

27 Conclusion It s about integrating best practices

28