uu.seUppsala University Publications
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Introducing Continuous Integration in an Enterprise Scale Environment
Uppsala University, Disciplinary Domain of Science and Technology, Mathematics and Computer Science, Department of Information Technology.
2008 (English)Independent thesis Advanced level (degree of Master (One Year)), 20 credits / 30 HE creditsStudent thesis
Abstract [en]

This thesis investigates how continuous integration best should be incorporated into a current development environment in order to acquire a shorter time for the regression testing feedback loop. The product in target is a high availability enterprise scale software product within mobile telecom. It utilizes a large commercial relational database for customer associated data and employs approximately one hundred designers.

A continuous integration system needs automatic database integration, compilation, testing, inspection, deployment, and feedback. Measures that are valuable to the build process regardless of build time should be given the highest priorities of implementation. Feedback has been developed in the form of Continuous Integration Web. The first priority at this stage is to introduce unit testing of the database which also has to be automatically built whenever updated or changed.

The amount of time used to integrate should be as close to ten minutes as possible. This goal is reachable if the build process is split into at least two integrations by differentiating unit tests from component tests and, if the software’s functionally divided parts are built separately on local integration servers.

Starting integrations automatically could potentially allow broken source code to reside in the source code repository. This problem can however be mitigated with the aid of good routines and sufficient communication between developers and the continuous integration server. If the latter is possible it is recommended to make use of a continuous integration server. Otherwise it is recommended to perform integrations manually.

Place, publisher, year, edition, pages
2008.
Series
UPTEC IT, ISSN 1401-5749 ; 08 014
Identifiers
URN: urn:nbn:se:uu:diva-88744OAI: oai:DiVA.org:uu-88744DiVA, id: diva2:158973
Presentation
(English)
Uppsok
Technology
Supervisors
Examiners
Available from: 2009-02-10 Created: 2009-02-05 Last updated: 2009-11-18Bibliographically approved

Open Access in DiVA

fulltext(1002 kB)1866 downloads
File information
File name FULLTEXT01.pdfFile size 1002 kBChecksum SHA-512
a8506bbece0d6563a6a6f70315e8ee3126c469345e8e04ade4129c2e674856eff2553fa3d8fdf9663798ced435ae66ab6edb40d7f00c7e01abd3bca09643b6c6
Type fulltextMimetype application/pdf

By organisation
Department of Information Technology

Search outside of DiVA

GoogleGoogle Scholar
Total: 1866 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 1158 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf