Seminar: Continuous Integration with Jenkins
When a software development project has left the first chaotic phase and matures to the add features and make corrections-phase, it is vital to ensure that the added features or corrections affect any of the already provided functions. This is especially complicated when many changes are delivered by many developers because it is often a challenge to understand what combination of changes that caused a problem. When the amount of test cases grows, the time to run them grows and this adds to the time for each change.
During this seminar, we briefly discuss how Continuous Integration handles this kind of problems, the consequences of moving a project to Continuous Integration, and how each developer will work in an environment with Continuous Integration.
Jenkins is a tool that is a Continuous Integration server that builds, runs tests and publishes the result. It is developed with the purpose of simplifying the moving of a project to Continuous Integration. We discuss the main functions of Jenkins and how to use them. We use the ArgoUML Open Source project as an example configuration of Jenkins.
About UppLYSning!
UppLYSning is the name for a series of seminars presented by the Lysator Academic Computer Club at the Linköping University. This seminar was held on November 22nd, 2011 at the Linköping University as part of UppLYSning.
About Linus Tolke!
Linus Tolke is a System Architect and Software Developer at Enea Experts in Linköping. He is experienced from many software development projects in different fields and tools. Since 2001 he contributes to the ArgoUML Open Source-project as project leader. ArgoUML is a UML-modelling tool written entirely in Java.
The seminar (in swedish) can be found here: Continuous Integration with Jenkins
