Setting up a Jenkins server

From TEIWiki
Revision as of 23:38, 24 May 2011 by Mholmes (talk | contribs) (New page: This page contains instructions and a script for setting up a Jenkins Continuous Integration Server for automated building of all of the TEI products. == What is a Jenkins server? == Th...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This page contains instructions and a script for setting up a Jenkins Continuous Integration Server for automated building of all of the TEI products.


What is a Jenkins server?

The purpose of a Jenkins server is to watch a code repository waiting for changes in the code. When it detects a change (because someone has edited one of the source code files), it downloads the changes and starts building the codebase to create an updated version of the project, whatever that is. In the case of the TEI, there are five different sub-projects, each of which is built separately: the Roma schema-building tool, the TEI Stylesheets, TEI P5, TEI P5 Documentation (the Guidelines etc.), and some TEI P5 test cases.


Why would I want to create a Jenkins server?