Importing Translated Kits - Revision history

Rdaly: /* WSDownload */

2017-01-30T23:06:14Z

WSDownload

← Older revision		Revision as of 23:06, 30 January 2017
Line 60:		Line 60:
	==WorldServer==		==WorldServer==
	===WSDownload===		===WSDownload===
	For Worldserver, the files are read from the <code>worldserver.in.location.path</code> configuration in '''config_l10n_vendor.properties'''. The files found in the FTP endpoint are moved to Lingoport_Data/LRM/staging/downloads/worldserver/		For Worldserver, the files are read from the <code>worldserver.in.location.path</code> configuration in '''config_l10n_vendor.properties'''. The files found in the FTP endpoint are moved to '''<HOME>/Lingoport_Data/LRM/staging/downloads/worldserver/'''

	They must conform to the zip structure and naming convention.		They must conform to the zip structure and naming convention.

	At that point, the files are ready to be imported. The Jenkins job '''WSDownload''' is in charge of that job.		At that point, the files are ready to be imported. The Jenkins job '''WSDownload''' is in charge of that job.

	== Moving the Prep Kit under staging ==		== Moving the Prep Kit under staging ==
	If that stage is successful, the files are then getting ready to be sent and are placed under the '''<HOME>/Lingoport_Data/LRM/staging/sendkits/lingotek''' or '''<HOME>/Lingoport_Data/LRM/staging/sendkits/ftp''' depending on the project configuration:		If that stage is successful, the files are then getting ready to be sent and are placed under the '''<HOME>/Lingoport_Data/LRM/staging/sendkits/lingotek''' or '''<HOME>/Lingoport_Data/LRM/staging/sendkits/ftp''' depending on the project configuration:

Rdaly at 23:05, 30 January 2017

2017-01-30T23:05:18Z

← Older revision		Revision as of 23:05, 30 January 2017
Line 58:		Line 58:
	</pre>		</pre>

			==WorldServer==
			===WSDownload===
			For Worldserver, the files are read from the <code>worldserver.in.location.path</code> configuration in '''config_l10n_vendor.properties'''. The files found in the FTP endpoint are moved to Lingoport_Data/LRM/staging/downloads/worldserver/

			They must conform to the zip structure and naming convention.

			At that point, the files are ready to be imported. The Jenkins job '''WSDownload''' is in charge of that job.
	== Moving the Prep Kit under staging ==		== Moving the Prep Kit under staging ==
	If that stage is successful, the files are then getting ready to be sent and are placed under the '''<HOME>/Lingoport_Data/LRM/staging/sendkits/lingotek''' or '''<HOME>/Lingoport_Data/LRM/staging/sendkits/ftp''' depending on the project configuration:		If that stage is successful, the files are then getting ready to be sent and are placed under the '''<HOME>/Lingoport_Data/LRM/staging/sendkits/lingotek''' or '''<HOME>/Lingoport_Data/LRM/staging/sendkits/ftp''' depending on the project configuration:

Rdaly at 23:00, 30 January 2017

2017-01-30T23:00:51Z

← Older revision		Revision as of 23:00, 30 January 2017
Line 10:		Line 10:

	The following sections details the locations of the files as they move through the system.		The following sections details the locations of the files as they move through the system.

			See [[Flow and Jobs]] for more information about FTP Jenkins jobs.


	== Lingotek ==		== Lingotek ==

Rdaly: /* FTPDownload */

2017-01-30T23:00:23Z

FTPDownload

← Older revision		Revision as of 23:00, 30 January 2017
Line 40:		Line 40:
	They must conform to the zip structure and naming convention.		They must conform to the zip structure and naming convention.

	At that point, the files are ready to be imported. The Jenkins job '''FTPDownload''' is in charge of that job~~. See [[Flow and Jobs]] for more information about FTP Jenkins jobs~~.		At that point, the files are ready to be imported. The Jenkins job '''FTPDownload''' is in charge of that job.

	=== FTPImport ===		=== FTPImport ===

Rdaly at 22:59, 30 January 2017

2017-01-30T22:59:58Z

← Older revision		Revision as of 22:59, 30 January 2017
Line 36:		Line 36:
	== FTP ==		== FTP ==
	=== FTPDownload ===		=== FTPDownload ===
			For FTP, the files are read from the <code>ftp.in.location.path</code> configuration in '''config_l10n_vendor.properties'''. The files found in the FTP endpoint are moved to '''<HOME>/Lingoport_Data/LRM/staging/downloads/ftp/'''.

			They must conform to the zip structure and naming convention.

			At that point, the files are ready to be imported. The Jenkins job '''FTPDownload''' is in charge of that job. See [[Flow and Jobs]] for more information about FTP Jenkins jobs.

	=== FTPImport ===		=== FTPImport ===
	The first step is to collect the files from the source directly, after a clean checkout/clone from the repository. If all is copacetic, the files to be send for translation are moved under the core LRM data directory, LRM_DATA_HOME, which is typically set to '''<HOME>/Lingoport_Data/LRM'''.		The first step is to collect the files from the source directly, after a clean checkout/clone from the repository. If all is copacetic, the files to be send for translation are moved under the core LRM data directory, LRM_DATA_HOME, which is typically set to '''<HOME>/Lingoport_Data/LRM'''.

Rdaly: /* Keeping Track under L10nStreamlining */

2017-01-30T22:29:26Z

Keeping Track under L10nStreamlining

← Older revision		Revision as of 22:29, 30 January 2017
Line 75:		Line 75:
	== Keeping Track under L10nStreamlining ==		== Keeping Track under L10nStreamlining ==
	L10nStreamlining helps keep track of what was sent and received. The last stage of the Prep Kit process is to move the files which were under		L10nStreamlining helps keep track of what was sent and received. The last stage of the Prep Kit process is to move the files which were under
	* <~~code~~>~/Lingoport_Data/LRM/staging/sendkits~~</code>~~		* '''<HOME>/Lingoport_Data/LRM/staging/sendkits'''
	over to		over to
	* <~~code~~>~/Lingoport_Data/L10nStreamlining/<group_name>/projects<project_name>/prepkits/~~PREP_KIT_2</code>~~.		* '''<HOME>/Lingoport_Data/L10nStreamlining/<group_name>/projects<project_name>/prepkits/PREP_KIT_X'''.

Rdaly: /* Moving the Prep Kit under staging */

2017-01-30T22:28:10Z

Moving the Prep Kit under staging

← Older revision		Revision as of 22:28, 30 January 2017
Line 50:		Line 50:

	== Moving the Prep Kit under staging ==		== Moving the Prep Kit under staging ==
	If that stage is successful, the files are then getting ready to be sent and are placed under the <HOME>/Lingoport_Data/LRM/staging/sendkits/lingotek or <HOME>/Lingoport_Data/LRM/staging/sendkits/ftp depending on the project configuration:		If that stage is successful, the files are then getting ready to be sent and are placed under the '''<HOME>/Lingoport_Data/LRM/staging/sendkits/lingotek''' or '''<HOME>/Lingoport_Data/LRM/staging/sendkits/ftp''' depending on the project configuration:
	<pre>		<pre>
	staging		<HOME>/Lingoport_Data/LRM/staging
	├── ...		├── ...
	├── sendkits		├── sendkits

Rdaly: /* Moving the Prep Kit under staging */

2017-01-30T22:27:34Z

Moving the Prep Kit under staging

← Older revision		Revision as of 22:27, 30 January 2017
Line 50:		Line 50:

	== Moving the Prep Kit under staging ==		== Moving the Prep Kit under staging ==
	If that stage is successful, the files are then getting ready to be sent and are placed under the <~~code~~>sendkits/lingotek~~</code>~~ or <~~code~~>sendkits/ftp~~</code>~~ depending on the project configuration:		If that stage is successful, the files are then getting ready to be sent and are placed under the <HOME>/Lingoport_Data/LRM/staging/sendkits/lingotek or <HOME>/Lingoport_Data/LRM/staging/sendkits/ftp depending on the project configuration:
	<pre>		<pre>
	staging		staging

Rdaly: /* LingotekImportKit */

2017-01-30T22:23:35Z

LingotekImportKit

← Older revision		Revision as of 22:23, 30 January 2017
Line 29:		Line 29:
	'''<HOME>/Lingoport_Data/LRM/staging/importkits/lingotek/<group_name>/<project_name>/TRANSLATED_KIT_<kit_version>_<locale>'''		'''<HOME>/Lingoport_Data/LRM/staging/importkits/lingotek/<group_name>/<project_name>/TRANSLATED_KIT_<kit_version>_<locale>'''
	to import into the source code.		to import into the source code.
	If successful, an email notifies the recipient and the proper [[Terms_and_Definitions#~~VCS~~\|VCS]] is invoked to push the files to the [[Terms_and_Definitions#repository\|repository]].		If successful, an email notifies the recipient and the proper [[Terms_and_Definitions#vcs\|VCS]] is invoked to push the files to the [[Terms_and_Definitions#repository\|repository]].

	Finally, for tracking purposes, a copy of the translated files retrieved from Lingotek is kept under		Finally, for tracking purposes, a copy of the translated files retrieved from Lingotek is kept under

Rdaly: /* LingotekImportKit */

2017-01-30T22:22:37Z

LingotekImportKit

← Older revision		Revision as of 22:22, 30 January 2017
Line 26:		Line 26:

	=== LingotekImportKit ===		=== LingotekImportKit ===
	This job uses the files under		This Jenkins job uses the files under
	<~~code~~>~/Lingoport_Data/LRM/staging/~~import_kits~~/lingotek/<group_name>/<project_name>/TRANSLATED_KIT_<kit_version>_<locale>~~</code>~~		'''<HOME>/Lingoport_Data/LRM/staging/importkits/lingotek/<group_name>/<project_name>/TRANSLATED_KIT_<kit_version>_<locale>'''
	to import into the source code.		to import into the source code.
	If successful, an email notifies the recipient and the proper VCS is invoked to push the files to the repository.		If successful, an email notifies the recipient and the proper [[Terms_and_Definitions#VCS\|VCS]] is invoked to push the files to the [[Terms_and_Definitions#repository\|repository]].

	Finally, for tracking purposes, a copy of the translated files retrieved from Lingotek is kept under		Finally, for tracking purposes, a copy of the translated files retrieved from Lingotek is kept under
	<~~code~~>~/L10nStreamlining/<group_name>/projects/<project_name>/importkits/TRANSLATED_KIT_<kit_version>_<locale>~~</code>~~		'''<HOME>/L10nStreamlining/<group_name>/projects/<project_name>/importkits/TRANSLATED_KIT_<kit_version>_<locale>'''

	== FTP ==		== FTP ==