Setting up a Jenkins server - Revision history

Mholmes: /* = NOTE: This documentation is out of date. */

2016-12-18T23:42:10Z

‎= NOTE: This documentation is out of date.

Mholmes: /* = NOTE: This documentation is out of date. */

2016-12-18T23:40:34Z

‎= NOTE: This documentation is out of date.

Mholmes: /* Stage three */

2015-12-14T16:18:23Z

‎Stage three

Mholmes: /* What does your script actually do? */

2015-12-14T16:17:50Z

‎What does your script actually do?

Mholmes: /* Why would I want to create a Jenkins server? */

2015-12-14T16:16:46Z

‎Why would I want to create a Jenkins server?

Mholmes at 12:35, 26 October 2015

2015-10-26T12:35:42Z

Mholmes: /* What is a Jenkins server? */

2014-07-02T11:23:29Z

‎What is a Jenkins server?

Rahtz: /* Why would I want to create a Jenkins server? */

2014-07-02T11:18:29Z

‎Why would I want to create a Jenkins server?

Rahtz: /* Why would I want to create a Jenkins server? */

2014-07-02T11:18:09Z

‎Why would I want to create a Jenkins server?

Mholmes: /* What does your script actually do? */

2013-04-02T01:16:46Z

‎What does your script actually do?

@@ Line 1: / Line 1: @@
 === NOTE: This documentation is out of date. ==
-Current work on setting up a Jenkins server for the TEI take the approach of building a Docker container. See the [TEI Jenkins repository https://github.com/TEIC/Jenkins/] for detailed information.
+Current work on setting up a Jenkins server for the TEI take the approach of building a Docker container. See the TEI Jenkins repository [https://github.com/TEIC/Jenkins/ https://github.com/TEIC/Jenkins/] for detailed information.
 ---

@@ Line 1: / Line 1: @@
 === NOTE: This documentation is out of date. ==
-The recent move of all the TEI development from SourceForge to GitHub has made the setup script below (which was already a bit out of date) no longer functional. It can be used as a guide to setting up your own server, but it will not work out of the box. This page will be updated with a new working script in due course.
+Current work on setting up a Jenkins server for the TEI take the approach of building a Docker container. See the [TEI Jenkins repository https://github.com/TEIC/Jenkins/] for detailed information.
 ---
 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? ==

@@ Line 53: / Line 53: @@
 == Stage three ==
-Download our [https://sourceforge.net/p/tei/code/HEAD/tree/trunk/Documents/Editing/Jenkins/jenkins_builder_script_2012.sh Jenkins_builder_script.sh] script from the TEI SourceForge repository. Get the script onto your server somehow. Make it executable, and run it as root. You'll see some basic explanatory information as it starts up. When the script completes, you should have a working Jenkins machine. The Jenkins GUI will be running on its default port of 8080, and if you connect to your server on that port, you should see it start to run the first of the seven TEI jobs. The first run takes a long time, because it has to download all the source code from SVN, but subsequent builds triggered by changes should be much quicker.
+Download our [https://github.com/TEIC/TEI/blob/dev/Documents/Editing/Jenkins/jenkins_builder_script_2012.sh Jenkins_builder_script.sh] script from the TEI GitHub repository. Get the script onto your server somehow. Make it executable, and run it as root. You'll see some basic explanatory information as it starts up. When the script completes, you should have a working Jenkins machine. The Jenkins GUI will be running on its default port of 8080, and if you connect to your server on that port, you should see it start to run the first of the seven TEI jobs. The first run takes a long time, because it has to download all the source code from GitHub, but subsequent builds triggered by changes should be much quicker.
 == Stage four ==

← Older revision		Revision as of 16:17, 14 December 2015
Line 71:		Line 71:
	== What does your script actually do? ==		== What does your script actually do? ==

−	Basically, the builder script adds some repositories and installs some software from them, including the Jenkins server software. Then it downloads some configuration files from the TEI SourceForge repository, tweaks them a bit, and restarts Jenkins. You can read the script itself in the [https://~~sourceforge~~.~~net~~/p/~~tei~~/~~code~~/~~HEAD/tree/trunk~~/Documents/Editing/Jenkins/jenkins_builder_script_2012.sh ~~SVN~~ repository].	+	Basically, the builder script adds some repositories and installs some software from them, including the Jenkins server software. Then it downloads some configuration files from the TEI SourceForge repository, tweaks them a bit, and restarts Jenkins. You can read the script itself in the [https://github.com/TEIC/TEI/blob/dev/Documents/Editing/Jenkins/jenkins_builder_script_2012.sh GitHub repository].

@@ Line 17: / Line 17: @@
 A Jenkins server is useful to project administrators because it will automatically create new builds whenever the codebase changes, so the admins don't have to remember to do that themselves. It will also notify you when a build fails, perhaps because a recent change to the source contained an error. Programmers working on the codebase can use this feature to check the changes they have made to make sure they're OK, and roll them back if they don't work, without having to have a complete build environment set up on their own computers.
-The TEI's main Jenkins server, in Oxford, is at [http://tei.it.ox.ac.uk/jenkins/ http://tei.it.ox.ac.uk/jenkins/]. There you can see the seven build targets and look at their status -- when they were last built, when the last build failure occurred, etc. The Humanities Computing and Media Centre at the University of Victoria also has a Jenkins server running at [http://teijenkins.hcmc.uvic.ca/ http://teijenkins.hcmc.uvic.ca/]. That server was built using the script below.
+The TEI's main Jenkins server, at the University of Victoria, is at [http://jenkins.tei-c.org http://jenkins.tei-c.org/]. There you can see the multiple build targets and look at their status -- when they were last built, when the last build failure occurred, etc. The University of Oxford also has a Jenkins server running at [http://jenkins2.tei-c.org/ http://jenkins2.tei-c.org/]. There is a third backup server running at [http://jenkins-paderborn.tei-c.org/ http://jenkins-paderborn.tei-c.org/].
 You might want to set up your own Jenkins server for a number of reasons:

← Older revision		Revision as of 12:35, 26 October 2015
Line 1:		Line 1:
		+	=== NOTE: This documentation is out of date. ==
		+	The recent move of all the TEI development from SourceForge to GitHub has made the setup script below (which was already a bit out of date) no longer functional. It can be used as a guide to setting up your own server, but it will not work out of the box. This page will be updated with a new working script in due course.
		+
		+	---
		+
	This page contains instructions and a script for setting up a Jenkins Continuous Integration Server for automated building of all of the TEI products.		This page contains instructions and a script for setting up a Jenkins Continuous Integration Server for automated building of all of the TEI products.

@@ Line 4: / Line 4: @@
 == What is a Jenkins server? ==
-Jenkins is a continuous integration server, a tool from modern software engineering. It's role is to notice whenever a change is made to the work-in-progress text of the TEI standard and perform a range of tasks, including building building each of the language variants and a number of tests. Jenkins catches a broad range of technical issues and complains very loudly about them to the users it thinks caused them.
+Jenkins is a continuous integration server, a tool from modern software engineering. Its role is to notice whenever a change is made to the work-in-progress text of the TEI standard and perform a range of tasks, including building building each of the language variants and a number of tests. Jenkins catches a broad range of technical issues and complains very loudly about them to the users it thinks caused them.
 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 seven different sub-projects, each of which is built separately: the OxGarage conversion server, the Roma schema-building tool, the TEI Stylesheets, an XSLT 1.0 version of the Stylesheets, TEI P5, TEI P5 Documentation (the Guidelines etc.), and some TEI P5 test cases. Some of these jobs depend on others -- for instance, all of the TEIP5-* projects are built using the stylesheets created from the Stylesheets project.

@@ Line 12: / Line 12: @@
 A Jenkins server is useful to project administrators because it will automatically create new builds whenever the codebase changes, so the admins don't have to remember to do that themselves. It will also notify you when a build fails, perhaps because a recent change to the source contained an error. Programmers working on the codebase can use this feature to check the changes they have made to make sure they're OK, and roll them back if they don't work, without having to have a complete build environment set up on their own computers.
-The TEI's main Jenkins server, in Oxford, is at [http://tei.oucs.ox.ac.uk/jenkins/ http://tei.oucs.ox.ac.uk/jenkins/]. There you can see the seven build targets and look at their status -- when they were last built, when the last build failure occurred, etc. The Humanities Computing and Media Centre at the University of Victoria also has a Jenkins server running at [http://teijenkins.hcmc.uvic.ca/ http://teijenkins.hcmc.uvic.ca/]. That server was built using the script below.
+The TEI's main Jenkins server, in Oxford, is at [http://tei.it.ox.ac.uk/jenkins/ http://tei.oucs.ox.ac.uk/jenkins/]. There you can see the seven build targets and look at their status -- when they were last built, when the last build failure occurred, etc. The Humanities Computing and Media Centre at the University of Victoria also has a Jenkins server running at [http://teijenkins.hcmc.uvic.ca/ http://teijenkins.hcmc.uvic.ca/]. That server was built using the script below.
 You might want to set up your own Jenkins server for a number of reasons:

← Older revision		Revision as of 01:16, 2 April 2013
Line 66:		Line 66:
	== What does your script actually do? ==		== What does your script actually do? ==

−	Basically, the builder script adds some repositories and installs some software from them, including the Jenkins server software. Then it downloads some configuration files from the TEI SourceForge repository, tweaks them a bit, and restarts Jenkins. You can read the script itself in the [~~http~~://~~tei.svn.~~sourceforge.net/~~viewvc~~/tei/trunk/Documents/Editing/Jenkins/jenkins_builder_script_2012.sh~~?content-type=text%2Fplain~~ SVN repository].	+	Basically, the builder script adds some repositories and installs some software from them, including the Jenkins server software. Then it downloads some configuration files from the TEI SourceForge repository, tweaks them a bit, and restarts Jenkins. You can read the script itself in the [https://sourceforge.net/p/tei/code/HEAD/tree/trunk/Documents/Editing/Jenkins/jenkins_builder_script_2012.sh SVN repository].