Chair for Applied Software Engineering Prof. B. Brügge, Ph. D.
Project Organization and Management, SS 2009 Exercise 5, May 20th 2009
1/1
Continuous Integration Exercise Managing Continuous Integration
You are a member of the management team of the Bumpers project. The project you are managing is a maintenance project to improve the existing code. In order to gain better insight into the projectʼs metrics and to help with the build process, set up a continuous integration server for the project and configure it for the development team so they can work on the four tasks described in a companion document for this exercise (see Part II).
Tasks:
1. Download the Bumpers source code Locate this URL:
http://wwwbruegge.in.tum.de/twiki/bin/view/Lehrstuhl/POMSS09Exercises Navigate to „Exercise Sheets“ and download Bumpers.zip
2. Set up the master repository
The SVN server already contains an empty repository for your team (named
“team#”, where # is the number of your team). Add the source code to your teams SVN repository by checking out the empty project, add the downloaded code to the “bumpers” repository and commit it.
Inform the development team that can start to become familiar with the code.
3. Set up a Hudson project
1. Create a new Job, give it the name of your team (“team#”) and choose the type of build project.
2. Enter SCM URL and credentials.
3. Configure the build trigger.
4. Add an ANT build step and invoke the target "all" of the build.xml file.
5. Extend the “all” target to include the execution of all unit tests 5. Configure the job to collect results of the unit test executions.
Inform the development team that they can start working on their tasks.
4. Monitor the progress of the development team
Keep track of defects and check the metrics of the project by successively adding code metrics plug-ins to the project (which metrics will be specified later).
Acceptance criteria:
• The continuous integration project is set up correctly on the CI server.
• The development team has finished their tasks and committed them.
• The system builds without any error messages.
• All problems reported in the metrics view of your project are gone (except checkstyle warnings - of those just eliminate as many as you can).
