Distributed Jenkins - Revision history

Olibouban at 20:31, 11 July 2018

2018-07-11T20:31:32Z

← Older revision		Revision as of 20:31, 11 July 2018
Line 109:		Line 109:
	On the master and slave nodes:		On the master and slave nodes:
	Open the 22 ports to and from the two systems to allow jobs to run from Master to Slaves/Agents/Nodes		Open the 22 ports to and from the two systems to allow jobs to run from Master to Slaves/Agents/Nodes
	Make sure the Outgoing ports and the Incoming ports for the Master and Slaves are allowed for ~~9000/other to allow~~ Dashboard upload.		Make sure the Outgoing ports and the Incoming ports for the Master and Slaves are allowed for Dashboard upload.

	*Whitelists for events going to the Continuous G11n System:		*Whitelists for events going to the Continuous G11n System:

Olibouban at 20:21, 11 July 2018

2018-07-11T20:21:27Z

← Older revision		Revision as of 20:21, 11 July 2018
Line 13:		Line 13:
	=== On GitHub ===		=== On GitHub ===
	Add a Pull Request Web Hook on the Git Repository, for example:		Add a Pull Request Web Hook on the Git Repository, for example:
	http://~~MASTERIPADDRESS:8080~~/buildByToken/buildWithParameters?job=Lingoport.SampleLite-DistributedPullRequest&token=HOOK		http://JENKINS_MASTER_IP_ADDRESS/buildByToken/buildWithParameters?job=Lingoport.SampleLite-DistributedPullRequest&token=HOOK

	The job name is the Master's job name for your project (not Lingoport.SampleLite-DistributedPullRequest)		The job name is the Master's job name for your project (not Lingoport.SampleLite-DistributedPullRequest)
Line 111:		Line 111:
	Make sure the Outgoing ports and the Incoming ports for the Master and Slaves are allowed for 9000/other to allow Dashboard upload.		Make sure the Outgoing ports and the Incoming ports for the Master and Slaves are allowed for 9000/other to allow Dashboard upload.

	*Whitelists for events going to ~~8080~~:		*Whitelists for events going to the Continuous G11n System:
	** BitBucket: 104.192.143.0/24		** BitBucket: 104.192.143.0/24
	** GitHub: 192.30.252.0/22		** GitHub: 192.30.252.0/22

Llawson: /* On GitHub */

2017-04-06T19:06:39Z

On GitHub

← Older revision		Revision as of 19:06, 6 April 2017
Line 13:		Line 13:
	=== On GitHub ===		=== On GitHub ===
	Add a Pull Request Web Hook on the Git Repository, for example:		Add a Pull Request Web Hook on the Git Repository, for example:
	http://MASTERIPADDRESS:8080/buildByToken/buildWithParameters?job=Lingoport.SampleLite-~~GitHubPullRequest~~&token=HOOK		http://MASTERIPADDRESS:8080/buildByToken/buildWithParameters?job=Lingoport.SampleLite-DistributedPullRequest&token=HOOK

	The job name is the Master's job name for your project (not Lingoport.SampleLite-~~GitHubPullRequest~~)		The job name is the Master's job name for your project (not Lingoport.SampleLite-DistributedPullRequest)

	=== Check the On-Boarding ===		=== Check the On-Boarding ===

Llawson: /* On Jenkins Master Node */

2017-04-06T19:04:41Z

On Jenkins Master Node

← Older revision		Revision as of 19:04, 6 April 2017
Line 5:		Line 5:

	=== On Jenkins Master Node ===		=== On Jenkins Master Node ===
	On the Master Node, copy the <code>Lingoport.SampleLite-~~GitHubPullRequest~~</code> and modify the Build Parameters:		On the Master Node, copy the <code>Lingoport.SampleLite-DistributedPullRequest</code> and modify the Build Parameters:
	* <code>GIT_REPO</code>: in the form <code>Lingoport/sandbox</code>		* <code>GIT_REPO</code>: in the form <code>Lingoport/sandbox</code>
	* <code>LITE_PROJECT_DEFINITION</code>: we recommend having a top level directory named 'lingoport' with a Lite project definition file in the repo itself.		* <code>LITE_PROJECT_DEFINITION</code>: we recommend having a top level directory named 'lingoport' with a Lite project definition file in the repo itself.

Olibouban: /* Node Installer */

2017-01-17T21:57:28Z

Node Installer

← Older revision		Revision as of 21:57, 17 January 2017
Line 73:		Line 73:
	** yum install epel-release		** yum install epel-release
	** yum install jq		** yum install jq
	* The remote scripts, <code>~~distributed_lite_pr~~.sh</code> ...)		* The remote scripts, <code>distributed_lite_ghpr.sh</code> ...)
	* A template <code>pullrequest-sonar-project.properties</code> under /var/lib/jenkins/lingoport/templates		* A template <code>pullrequest-sonar-project.properties</code> under /var/lib/jenkins/lingoport/templates
	** A number of items need to be set in the templates itself, including GitHub's username/OAuth Token, Dashboard Username / Password for all the project to be handled.		** A number of items need to be set in the templates itself, including GitHub's username/OAuth Token, Dashboard Username / Password for all the project to be handled.

Olibouban: /* On-boarding a Distributed GitHub Pull Request Jenkins Job */

2016-12-29T22:34:07Z

On-boarding a Distributed GitHub Pull Request Jenkins Job

← Older revision		Revision as of 22:34, 29 December 2016
Line 3:		Line 3:
	== On-boarding a Distributed GitHub Pull Request Jenkins Job==		== On-boarding a Distributed GitHub Pull Request Jenkins Job==
	Once Jenkins is setup in Master/Slave mode (See below for setup), the following instructions will help to on-board a GitHub Pull Request job which will be initiated by a Webhook triggering a Master Jenkins job which in turns will execute the job on a slave node.		Once Jenkins is setup in Master/Slave mode (See below for setup), the following instructions will help to on-board a GitHub Pull Request job which will be initiated by a Webhook triggering a Master Jenkins job which in turns will execute the job on a slave node.


	=== On Jenkins Master Node ===		=== On Jenkins Master Node ===

Olibouban: /* On BitBucket */

2016-12-29T22:33:42Z

On BitBucket

← Older revision		Revision as of 22:33, 29 December 2016
Line 29:		Line 29:
	Add a Web Hook on the Git Repository in the following form:		Add a Web Hook on the Git Repository in the following form:
	http://MASTERIPADDRESS:<MASTERPORT>/bitbucket-hook/		http://MASTERIPADDRESS:<MASTERPORT>/bitbucket-hook/
			for example:
			http://i18n.jenkins.company/bitbucket-hook/

	This hook will have a BITBUCKET_PAYLOAD JSON file and will trigger the execution of ~~the~~ job on-boarded with ~~the~~ BitBucket Git repository. For more information, see https://wiki.jenkins-ci.org/display/JENKINS/BitBucket+Plugin.		This hook will have a BITBUCKET_PAYLOAD JSON file and will trigger the execution of any job on-boarded with that BitBucket Git repository. For more information, see https://wiki.jenkins-ci.org/display/JENKINS/BitBucket+Plugin.

	== Master/Slave Jenkins Setup ==		== Master/Slave Jenkins Setup ==

Olibouban: /* On-boarding a Distributed BitBucket Pull Request Jenkins Job */

2016-12-29T22:32:24Z

On-boarding a Distributed BitBucket Pull Request Jenkins Job

← Older revision		Revision as of 22:32, 29 December 2016
Line 30:		Line 30:
	http://MASTERIPADDRESS:<MASTERPORT>/bitbucket-hook/		http://MASTERIPADDRESS:<MASTERPORT>/bitbucket-hook/

	This hook will have a BITBUCKET_PAYLOAD JSON file and will trigger the execution of the job on-boarded with the BitBucket Git repository.		This hook will have a BITBUCKET_PAYLOAD JSON file and will trigger the execution of the job on-boarded with the BitBucket Git repository. For more information, see https://wiki.jenkins-ci.org/display/JENKINS/BitBucket+Plugin.

	== Master/Slave Jenkins Setup ==		== Master/Slave Jenkins Setup ==

Olibouban: /* On-boarding a Distributed BitBucket Pull Request Jenkins Job */

2016-12-29T22:31:45Z

On-boarding a Distributed BitBucket Pull Request Jenkins Job

← Older revision		Revision as of 22:31, 29 December 2016
Line 25:		Line 25:

	<b>Note:</b> Make sure the BitBucket 'Branches to Build' is set to 'any' (**)		<b>Note:</b> Make sure the BitBucket 'Branches to Build' is set to 'any' (**)

			=== On BitBucket ===
			Add a Web Hook on the Git Repository in the following form:
			http://MASTERIPADDRESS:<MASTERPORT>/bitbucket-hook/

			This hook will have a BITBUCKET_PAYLOAD JSON file and will trigger the execution of the job on-boarded with the BitBucket Git repository.

	== Master/Slave Jenkins Setup ==		== Master/Slave Jenkins Setup ==

Olibouban at 22:28, 29 December 2016

2016-12-29T22:28:58Z

← Older revision		Revision as of 22:28, 29 December 2016
Line 4:		Line 4:
	Once Jenkins is setup in Master/Slave mode (See below for setup), the following instructions will help to on-board a GitHub Pull Request job which will be initiated by a Webhook triggering a Master Jenkins job which in turns will execute the job on a slave node.		Once Jenkins is setup in Master/Slave mode (See below for setup), the following instructions will help to on-board a GitHub Pull Request job which will be initiated by a Webhook triggering a Master Jenkins job which in turns will execute the job on a slave node.

	~~== On-boarding a Distributed BitBucket Pull Request Jenkins Job==~~
	Once Jenkins is setup in Master/Slave mode (See below for setup), the following instructions will help to on-board a BitBucket Pull Request job which will be initiated by a Webhook triggering a Master Jenkins job which in turns will execute the job on a slave node.

	=== On Jenkins Master Node ===		=== On Jenkins Master Node ===
Line 22:		Line 20:
	=== Check the On-Boarding ===		=== Check the On-Boarding ===
	Test the system by creating a test pull request, for instance with an Embedded String commit.		Test the system by creating a test pull request, for instance with an Embedded String commit.

			== On-boarding a Distributed BitBucket Pull Request Jenkins Job==
			Once Jenkins is setup in Master/Slave mode (See below for setup), the following instructions will help to on-board a BitBucket Pull Request job which will be initiated by a Webhook triggering a Master Jenkins job which in turns will execute the job on a slave node.

			<b>Note:</b> Make sure the BitBucket 'Branches to Build' is set to 'any' (**)

	== Master/Slave Jenkins Setup ==		== Master/Slave Jenkins Setup ==