Software Engineering II - Exercise

Size: px

Start display at page:

Download "Software Engineering II - Exercise"

Clyde Merritt
10 years ago
Views:

1 Software Engineering II - Exercise May 20 th 2009 Continuous Integration Bernd Bruegge Hans Breidler, Helmut Naughton, Florian Schneider Applied Software Engineering Technische Universitaet Muenchen 1

Helmut Naughton, Florian Schneider Applied Software

2 Purpose of this exercise Target group: future managers Desired outcome: Appreciate the problems of setting up CI Understand CI as a useful tool for establishing the status of a project Learn how to turn the information into action Understand that CI is not about personal performance evaluation Information sharing: 2 Handouts describing the exercises Managing Continuous Integration Development with Continuous integration 1 Handout with solution to Hudson setup (handed out after min) 2

CI is not about personal performance evaluation Information sharing: 2 Handouts describing the exercises Managing

3 Today s exercise: Team assignment Team 1 Markus Hornauer Stefan Birnkammerer Marco Aust Michael Hausmann Dong Li Barbara Köhler Stephan Krusche Team 3 Zahra Ammari Christoph Baechtle David Binder Grigory Markin Michaela Ranner Andrii Shyshkalov Team 2 Martin Schuster Andreas Mirbeth Stephan Köhler Daniel Nyga Tobias Weiherer Team 4 Petromil Petkov Raphael Haase Manuel Then Erik Aberg Marc Hoffmann Mathias Messmer 3

Markin Michaela Ranner Andrii Shyshkalov Team 2 Martin Schuster Andreas Mirbeth Stephan Köhler Daniel

4 Today s exercise: Outline Exercise Overview Decide who will be in the following sub-teams: Development team Management team Follow the instructions on the sheets that will be handed out One sheet per subteam Acceptance test The group meeting the acceptance criteria closest will get ice-cream from the Cafeteria 4

on the sheets that will be handed out One sheet per subteam Acceptance test

5 Why continuous integration? Building multiple product lines Quality assurance Measure progress Gather code metrics Opportunistic release management 5

6 Development team Tasks: Read documentation on the Bumpers project Checkout source code into your workspace Implement test and some refactorings Incorporate input from the management team 6

7 Management team Tasks: Create a Hudson CI project for your team Check in the project s source code Setup metrics for the project Monitor metrics Give tasks to the development team 7

8 Infrastructure WLAN: POM09 WPA/personal password pom09pom09 If you cannot get an IP address via DHCP assign your own IP > (Subnet ) Server IP Hudson Website Subversion Server svn:// (add team# for repository location) Login is your surname (lower case, no umlauts (ae), Password is pom09 8

0.1.5:8080 Subversion Server svn://10.0.1.5 (add team# for repository location) Login

9 Metrics The management team should now add the following targets to your all ant task and configure your Hudson job to display the results: PMD: target pmd see Identify the problems and instruct the development team to fix them. Findbugs: target findbugs Prioritize the problems and assign tasks to the development team. Checkstyle: target checkstyle Gain an overview of problems reported by checkstyle and offer a solution not involving removing them all by hand. 9

Findbugs: target findbugs http://findbugs.sourceforge.net/ Prioritize the problems and assign tasks to the development team.

10 Exercise continued The exercise is over but I ll post the server address for anyone who wants to play some more The new CI server address is and the new SVN address is svn://lapbruegge69.informatik.tu-muenchen.de/ team# 10

address is http://lapbruegge69.informatik.tumuenchen.

Improving Software Quality with the Continuous Integration Server Hudson. Dr. Ullrich Hafner Avaloq Evolution AG 8911

Improving Software Quality with the Continuous Integration Server Hudson Dr. Ullrich Hafner Avaloq Evolution AG 8911 AGENDA 2 > INTRODUCTION TO CI AND HUDSON > USING STATIC ANALYSIS IN PROJECTS > DEMO