Flow and Jobs - Revision history

Rdaly: /* Prep Kits */

2017-02-01T20:51:39Z

Prep Kits

← Older revision		Revision as of 20:51, 1 February 2017
Line 141:		Line 141:
	This is the default tab. The jobs on this tab are triggered by an actual user who must have permissions.		This is the default tab. The jobs on this tab are triggered by an actual user who must have permissions.

	One Jenkins automation job is on-boarded for each repository project. The Jenkins jobs calls <code>job_prepkit.sh</code>. The Jenkins job name is composed of the group name and the project name in the form <code><group_name>.<project_name>-PrepKit</code>.		One Jenkins automation job is on-boarded for each repository project. The Jenkins jobs calls <code>job_prepkit.sh</code>. The Jenkins job name is composed of the group name and the project name in the form '''<code><group_name>.<project_name>-PrepKit</code>'''.

	A Prep Kit job follows the following steps:		A Prep Kit job follows the following steps:

Rdaly: /* Nightlies */

2017-02-01T20:50:55Z

Nightlies

← Older revision		Revision as of 20:50, 1 February 2017
Line 130:		Line 130:

	= Nightlies =		= Nightlies =
	One Jenkins automation job is on-boarded for each repository project. The Jenkins jobs calls <code>job_nightly.sh</code>. The Jenkins job name is composed of the group name and the project name in the form <code><group_name>.<project_name>-Nightly</code>.		One Jenkins automation job is on-boarded for each repository project. The Jenkins jobs calls <code>job_nightly.sh</code>. The Jenkins job name is composed of the group name and the project name in the form '''<code><group_name>.<project_name>-Nightly</code>'''.

	In addition to what the Automation jobs do, the Nightly job also sends two emails on a configured frequency.		In addition to what the Automation jobs do, the Nightly job also sends two emails on a configured frequency.

Rdaly: /* Automation */

2017-02-01T20:50:04Z

Automation

← Older revision		Revision as of 20:50, 1 February 2017
Line 120:		Line 120:

	The following steps are taken:		The following steps are taken:
	* The repository files are checked out anew (not update, no pull, a clean copy). Jenkins keeps the source code under <code>~~/var/lib/jenkins~~/jobs/<group_name>.<project_name>/workspace/</code>		* The repository files are checked out anew (not update, no pull, a clean copy). Jenkins keeps the source code under <code><HOME>/jobs/<group_name>.<project_name>/workspace/</code>
	* The LRM XML reports are typically generated under <code><HOME>/Lingoport_Data/Dashboard/Projects/group_name.project_name/LRMScans</code>		* The LRM XML reports are typically generated under <code><HOME>/Lingoport_Data/Dashboard/Projects/group_name.project_name/LRMScans</code>
	* The Lingoport Dashboard is updated using the XML reports and relies on the above location for those XML generated reports.		* The Lingoport Dashboard is updated using the XML reports and relies on the above location for those XML generated reports.

Rdaly: /* Automation */

2017-02-01T20:49:19Z

Automation

← Older revision		Revision as of 20:49, 1 February 2017
Line 120:		Line 120:

	The following steps are taken:		The following steps are taken:
	* The repository files are checked out anew (not update, no pull, a clean copy). ~~Newer versions of~~ Jenkins ~~keep~~ the source code under <code>/var/lib/jenkins/jobs/<group_name>.<project_name>/workspace/</code>		* The repository files are checked out anew (not update, no pull, a clean copy). Jenkins keeps the source code under <code>/var/lib/jenkins/jobs/<group_name>.<project_name>/workspace/</code>
	* The LRM XML reports are typically generated under <code><HOME>/Lingoport_Data/Dashboard/Projects/group_name.project_name/LRMScans</code>		* The LRM XML reports are typically generated under <code><HOME>/Lingoport_Data/Dashboard/Projects/group_name.project_name/LRMScans</code>
	* The Lingoport Dashboard is updated using the XML reports and relies on the above location for those XML generated reports.		* The Lingoport Dashboard is updated using the XML reports and relies on the above location for those XML generated reports.

Rdaly: /* Automation */

2017-02-01T20:48:56Z

Automation

← Older revision		Revision as of 20:48, 1 February 2017
Line 120:		Line 120:

	The following steps are taken:		The following steps are taken:
	* The repository files are checked out anew (not update, no pull, a clean copy). Newer versions of Jenkins keep the source code under <code>/var/lib/jenkins/<group_name>.<project_name>/workspace/</code>		* The repository files are checked out anew (not update, no pull, a clean copy). Newer versions of Jenkins keep the source code under <code>/var/lib/jenkins/jobs/<group_name>.<project_name>/workspace/</code>
	* The LRM XML reports are typically generated under <code><HOME>/Lingoport_Data/Dashboard/Projects/group_name.project_name/LRMScans</code>		* The LRM XML reports are typically generated under <code><HOME>/Lingoport_Data/Dashboard/Projects/group_name.project_name/LRMScans</code>
	* The Lingoport Dashboard is updated using the XML reports and relies on the above location for those XML generated reports.		* The Lingoport Dashboard is updated using the XML reports and relies on the above location for those XML generated reports.

Rdaly at 20:47, 1 February 2017

2017-02-01T20:47:21Z

Rdaly at 20:17, 1 February 2017

2017-02-01T20:17:54Z

← Older revision		Revision as of 20:17, 1 February 2017
Line 4:		Line 4:
	[[File:Jenkins_LRM_Tabs.jpg]]		[[File:Jenkins_LRM_Tabs.jpg]]

	The job is named <group name>.<project name>. In this case, the group name is "~~blue~~" and the project name is "globalyzerswing". Lingoport recommends using this naming convention.		This illustration shows the job Blue.globalyzerswing under the Automation tab. The job is named <group name>.<project name>. In this case, the group name is "Blue" and the project name is "globalyzerswing". Lingoport recommends using this naming convention and many of the Jenkins jobs expect this.

	= Infrastructure =		= Infrastructure =

Rdaly: /* WSImport */

2017-02-01T20:14:36Z

WSImport

← Older revision		Revision as of 20:14, 1 February 2017
Line 104:		Line 104:
	The Jenkins WSImport job calls the <code>ws_import.sh</code> script under <code><HOME>/lingoport/lrm-server-x.y/bin</code>.		The Jenkins WSImport job calls the <code>ws_import.sh</code> script under <code><HOME>/lingoport/lrm-server-x.y/bin</code>.

	Worldserver files that are to be imported must have been downloaded (See WSDownload) under <code><LRM_DATA_HOME>/downloads/worldserver</code>. The following steps are taken:		Worldserver files that are to be imported must have been downloaded (See WSDownload) under <code><LRM_DATA_HOME>/staging/downloads/worldserver</code>. The following steps are taken:
	* Executes the checks on the translated files with regards to the project and the version of the kit		* Executes the checks on the translated files with regards to the project and the version of the kit
	* If the checks pass, copy the translated files in a cleanly checked out project		* If the checks pass, copy the translated files in a cleanly checked out project

Rdaly at 19:55, 1 February 2017

2017-02-01T19:55:43Z

← Older revision		Revision as of 19:55, 1 February 2017
Line 4:		Line 4:
	[[File:Jenkins_LRM_Tabs.jpg]]		[[File:Jenkins_LRM_Tabs.jpg]]

	The job is named <group name>.<project name>. In this case, the group name is "blue" and the project name is		The job is named <group name>.<project name>. In this case, the group name is "blue" and the project name is "globalyzerswing". Lingoport recommends using this naming convention.

	= Infrastructure =		= Infrastructure =
	Those jobs are common to all [[Terms_and_Definitions#onboarding\|on-boarded]] projects and need to be set up once during installation and configuration.		Those jobs are common to all [[Terms_and_Definitions#onboarding\|on-boarded]] projects and need to be set up once during installation and configuration.

Rdaly at 19:54, 1 February 2017

2017-02-01T19:54:48Z

← Older revision		Revision as of 19:54, 1 February 2017
Line 4:		Line 4:
	[[File:Jenkins_LRM_Tabs.jpg]]		[[File:Jenkins_LRM_Tabs.jpg]]

			The job is named <group name>.<project name>. In this case, the group name is "blue" and the project name is
	= Infrastructure =		= Infrastructure =
	Those jobs are common to all [[Terms_and_Definitions#onboarding\|on-boarded]] projects and need to be set up once during installation and configuration.		Those jobs are common to all [[Terms_and_Definitions#onboarding\|on-boarded]] projects and need to be set up once during installation and configuration.

← Older revision		Revision as of 20:47, 1 February 2017
Line 4:		Line 4:
	[[File:Jenkins_LRM_Tabs.jpg]]		[[File:Jenkins_LRM_Tabs.jpg]]

	This illustration shows the job Blue.globalyzerswing under the Automation tab. The job is named <group name>.<project name>. In this case, the group name is "Blue" and the project name is "globalyzerswing". Lingoport recommends using this naming convention and many of the Jenkins jobs expect this.		This illustration shows the job '''Blue.globalyzerswing''' under the '''Automation''' tab. The job is named <group name>.<project name>. In this case, the group name is "Blue" and the project name is "globalyzerswing". Lingoport recommends using this naming convention and many of the Jenkins jobs expect this.

	= Infrastructure =		= Infrastructure =
Line 71:		Line 71:
	The Jenkins FTPImport job calls the <code>ftp_import.sh</code> script under <code><HOME>/lingoport/lrm-server-x.y/bin</code>.		The Jenkins FTPImport job calls the <code>ftp_import.sh</code> script under <code><HOME>/lingoport/lrm-server-x.y/bin</code>.

	FTP files to be imported must have been downloaded (See FTPDownload) under <code><LRM_DATA_HOME>/downloads/ftp</code>. The following steps are taken:		FTP files to be imported must have been downloaded (See FTPDownload) under <code><LRM_DATA_HOME>/staging/downloads/ftp</code>. The following steps are taken:
	* Executes the checks on the translated files with regards to the project and the version of the kit		* Executes the checks on the translated files with regards to the project and the version of the kit
	* If the checks pass, copy the translated files in a cleanly checked out project		* If the checks pass, copy the translated files in a cleanly checked out project
Line 120:		Line 120:

	The following steps are taken:		The following steps are taken:
	* The repository files are checked out anew (not update, no pull, a clean copy). Newer versions of Jenkins keep the source code under <code>/var/lib/jenkins~~/workspace~~/<group_name>.<project_name></code>		* The repository files are checked out anew (not update, no pull, a clean copy). Newer versions of Jenkins keep the source code under <code>/var/lib/jenkins/<group_name>.<project_name>/workspace/</code>
	* The LRM ~~xml~~ reports are typically generated under <code><HOME>/Lingoport_Data/Dashboard/Projects/group_name.project_name/LRMScans</code>		* The LRM XML reports are typically generated under <code><HOME>/Lingoport_Data/Dashboard/Projects/group_name.project_name/LRMScans</code>
	* The Lingoport Dashboard is updated using the XML reports and relies on the above location for those ~~xml~~ generated reports.		* The Lingoport Dashboard is updated using the XML reports and relies on the above location for those XML generated reports.
	* The base files are pseudo-localized and committed to the repository		* The base files are pseudo-localized and committed to the repository

	The automation jobs can be triggered by a Git push or an SVN commit depending on the availability of Webhooks on the repositories. If those triggers are not set, the Nightly jobs will take care of doing something similar at least once a day, so the Dashboard and the Pseudo-localization is at most a day behind the development team commits.		The automation jobs can be triggered by a Git push or an SVN commit depending on the availability of Webhooks on the repositories. If those triggers are not set, the Nightly jobs will take care of doing something similar at least once a day, so the Dashboard and the Pseudo-localization is at most a day behind the development team commits.

	To make sure the Dashboard is up to date, the Automation job can be manually triggered.		To make sure the Lingoport Dashboard is up to date, the Automation job can be manually triggered.

	= Nightlies =		= Nightlies =
Line 136:		Line 136:
	* A late prep kit notification if applicable: Each prep kit sent for translation has a due date, and kits which are behind are noted.		* A late prep kit notification if applicable: Each prep kit sent for translation has a due date, and kits which are behind are noted.

	Nightlies are triggered by a cron-like scheduler, typically every night.		Nightlies are triggered by a cron-like scheduler in Jenkins, typically every night.

	= Prep Kits =		= Prep Kits =
Line 145:		Line 145:
	A Prep Kit job follows the following steps:		A Prep Kit job follows the following steps:
	* Take the latest source code from the repository in a empty directory		* Take the latest source code from the repository in a empty directory
	* Analyze the configured resource bundles and copies the files to be translated under <code>staging/sendkits/<l10nvendor>/<group_name>/<project_name>/PREP_KIT_x/<locale></code>		* Analyze the configured resource bundles and copies the files to be translated under <code><LRM_DATA_HOME>/staging/sendkits/<l10nvendor>/<group_name>/<project_name>/PREP_KIT_x/<locale></code>
	* Sends those files to the L10n vendor (for instance Lingotek)		* Sends those files to the L10n vendor (for instance Lingotek)
	* Remove the files from the staging area.		* Remove the files from the staging area.
	** Note: If sending the files to the L10n vendor fails, for instance because of a network outage, the files are kept under staging. The Infractructure '~~checksend~~' job will use those files when the corrective action (network is back) has been taken.		** Note: If sending the files to the L10n vendor fails, for instance because of a network outage, the files are kept under staging. The Infractructure 'CheckSend' job will use those files when the corrective action (network is back) has been taken.
	* Notifies the configured recipient a Prep Kit has been sent		* Notifies the configured recipient a Prep Kit has been sent
	* Determines a due date for each locale		* Determines a due date for each locale
Line 154:		Line 154:

	= LicenseExpiration =		= LicenseExpiration =
	* One Jenkins License Expiration job is on-boarded for each licensed group. The Jenkins jobs calls <code>~~$LRM_HOME~~/bin/job_checklicense.sh 30</code> if 30 days is the threshold to start notification the license is about to expire. The Jenkins job name is composed of the group name and <code>License_Expiration</code> in the form <code> <group_name>.LicenseExpiration</code>.		* One Jenkins License Expiration job is on-boarded for each licensed group. The Jenkins jobs calls <code><HOME>/lingoport/lrm-server-x.y/bin/job_checklicense.sh 30</code> if 30 days is the threshold to start notification the license is about to expire. The Jenkins job name is composed of the group name and <code>License_Expiration</code> in the form <code> <group_name>.LicenseExpiration</code>.
	*The jobs on this tab are triggered every week.		*The jobs on this tab are triggered every week.
	*An E-Mail Notification post-build action must specify the recipients of the license expiration.		*An E-Mail Notification post-build action must specify the recipients of the license expiration.