Prepping a Kit - Revision history

Rdaly: /* Sending the Files under staging */

2017-01-30T20:54:23Z

Sending the Files under staging

← Older revision		Revision as of 20:54, 30 January 2017
Line 39:		Line 39:
	If this has been successful, the next step is to send the files to Lingotek or FTP, depending on the configuration. This may fail due to network problems, server saturation, or other causes. Until the files have successfully been sent, they are kept under '''staging'''.		If this has been successful, the next step is to send the files to Lingotek or FTP, depending on the configuration. This may fail due to network problems, server saturation, or other causes. Until the files have successfully been sent, they are kept under '''staging'''.

	<b>If the files were not sent, <code>check_send</code> will later on pick up here in the process</b>		<b>If the files were not sent, the Jenkins job <code>check_send</code> will later on pick up here in the process</b>

	== Keeping Track under L10nStreamlining ==		== Keeping Track under L10nStreamlining ==

Rdaly: /* Sending the Files under staging */

2017-01-30T20:54:03Z

Sending the Files under staging

← Older revision		Revision as of 20:54, 30 January 2017
Line 37:		Line 37:

	== Sending the Files under staging ==		== Sending the Files under staging ==
	If this has been successful, the next step is to send the files to Lingotek or FTP, depending on the configuration. This may fail due to network problems, server saturation, or other causes. Until the files have successfully been sent, they are kept under staging.		If this has been successful, the next step is to send the files to Lingotek or FTP, depending on the configuration. This may fail due to network problems, server saturation, or other causes. Until the files have successfully been sent, they are kept under '''staging'''.

	<b>If the files were not sent, <code>check_send</code> will later on pick up here in the process</b>		<b>If the files were not sent, <code>check_send</code> will later on pick up here in the process</b>

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

2017-01-30T20:50:01Z

Moving the Prep Kit under staging

← Older revision		Revision as of 20:50, 30 January 2017
Line 18:		Line 18:

	== 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 '''sendkits/lingotek''' or '''sendkits/ftp''' depending on the project configuration:
	<pre>		<pre>
	staging		<HOME>/Lingoport_Data/LRM/staging
	├── ...		├── ...
	├── sendkits		├── sendkits

Rdaly: /* From Source to core LRM data */

2017-01-30T20:48:45Z

From Source to core LRM data

← Older revision		Revision as of 20:48, 30 January 2017
Line 5:		Line 5:

	== From Source to core LRM data ==		== From Source to core LRM data ==
	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 sent for translation are moved under the core LRM data directory, LRM_DATA_HOME, which is typically set to '''~/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 sent for translation are moved under the core LRM data directory, LRM_DATA_HOME, which is typically set to '''<HOME>/Lingoport_Data/LRM'''.

	For instance, if this is the ''second'' prep kit, the base files would be moved under:		For instance, if this is the ''second'' prep kit, the base files would be moved under:

	<pre>		<pre>
	<group_name>		<HOME>/Lingoport_Data/LRM/<group_name>
	├── logs		├── logs
	├── prep_kit		├── prep_kit

Rdaly: /* From Source to core LRM data */

2017-01-30T20:47:11Z

From Source to core LRM data

← Older revision		Revision as of 20:47, 30 January 2017
Line 5:		Line 5:

	== From Source to core LRM data ==		== From Source to core LRM data ==
	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 ~/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 sent for translation are moved under the core LRM data directory, LRM_DATA_HOME, which is typically set to '''~/Lingoport_Data/LRM'''.

	For instance, if this is the second prep kit, the base files would be moved under:		For instance, if this is the ''second'' prep kit, the base files would be moved under:

	<pre>		<pre>
Line 13:		Line 13:
	├── logs		├── logs
	├── prep_kit		├── prep_kit
	│ └── <~~project~~>		│ └── <project_name>
	│ └── PREP_KIT_2		│ └── PREP_KIT_2
	</pre>		</pre>

Rdaly at 20:45, 30 January 2017

2017-01-30T20:45:02Z

← Older revision		Revision as of 20:45, 30 January 2017
Line 1:		Line 1:

	The '''<group_name>.<project_name>-PrepKit''' 'build' Jenkins job to preps a kit. It collects the right files, checking for correctness and sends them to the appropriate location, finally notifying the recipients. During this process files move to different locations to ensure they are delivered properly or they can be delivered properly later if some malfunction happened, for instance due to a network outage.		The '''<group_name>.<project_name>-PrepKit''' 'build' Jenkins job preps a kit. It collects the right files, checking for correctness and sends them to the appropriate location, finally notifying the recipients. During this process files move to different system locations to ensure they are delivered properly or they can be delivered properly later if some malfunction happened, for instance due to a network outage.

	This section describes how the files are moved.		This section describes how the files are moved.

Rdaly at 20:44, 30 January 2017

2017-01-30T20:44:21Z

← Older revision		Revision as of 20:44, 30 January 2017
Line 1:		Line 1:

	~~When executing the~~ <group_name>.<project_name>-PrepKit 'build' job to ~~prep~~ a kit~~, <i>i.e~~. ~~collecting~~ the right files, checking for correctness~~, sending~~ them to the appropriate location, ~~and~~ notifying the recipients~~</i>,~~ files move to different locations to ensure they are delivered properly or they can be delivered properly later if some malfunction happened, for instance due to a network outage.		The '''<group_name>.<project_name>-PrepKit''' 'build' Jenkins job to preps a kit. It collects the right files, checking for correctness and sends them to the appropriate location, finally notifying the recipients. During this process files move to different locations to ensure they are delivered properly or they can be delivered properly later if some malfunction happened, for instance due to a network outage.

	This section describes how the files are moved.		This section describes how the files are moved.

Olibouban at 23:04, 15 April 2015

2015-04-15T23:04:19Z

← Older revision		Revision as of 23:04, 15 April 2015
Line 2:		Line 2:
	When executing the <group_name>.<project_name>-PrepKit 'build' job to prep a kit, <i>i.e. collecting the right files, checking for correctness, sending them to the appropriate location, and notifying the recipients</i>, files move to different locations to ensure they are delivered properly or they can be delivered properly later if some malfunction happened, for instance due to a network outage.		When executing the <group_name>.<project_name>-PrepKit 'build' job to prep a kit, <i>i.e. collecting the right files, checking for correctness, sending them to the appropriate location, and notifying the recipients</i>, files move to different locations to ensure they are delivered properly or they can be delivered properly later if some malfunction happened, for instance due to a network outage.

	This section describes how the files are moved		This section describes how the files are moved.

	== From Source to core LRM data ==		== From Source to core LRM data ==

Olibouban: /* Sending the Files under staging */

2015-04-15T23:00:06Z

Sending the Files under staging

← Older revision		Revision as of 23:00, 15 April 2015
Line 39:		Line 39:
	If this has been successful, the next step is to send the files to Lingotek or FTP, depending on the configuration. This may fail due to network problems, server saturation, or other causes. Until the files have successfully been sent, they are kept under staging.		If this has been successful, the next step is to send the files to Lingotek or FTP, depending on the configuration. This may fail due to network problems, server saturation, or other causes. Until the files have successfully been sent, they are kept under staging.

	<b>If the files were not sent, <code>check_send</b> will later on pick up here in the process</b>		<b>If the files were not sent, <code>check_send</code> will later on pick up here in the process</b>

	== Keeping Track under L10nStreamlining ==		== Keeping Track under L10nStreamlining ==

Olibouban: /* Sending the Files under staging */

2015-04-15T22:59:48Z

Sending the Files under staging

← Older revision		Revision as of 22:59, 15 April 2015
Line 37:		Line 37:

	== Sending the Files under staging ==		== Sending the Files under staging ==
	If this has been successful, the next step is to send the files to Lingotek or FTP, depending on the configuration. This may fail due to network problems, server saturation, or other causes. Until the files have successfully been sent, they are kept under staging.		If this has been successful, the next step is to send the files to Lingotek or FTP, depending on the configuration. This may fail due to network problems, server saturation, or other causes. Until the files have successfully been sent, they are kept under staging.

			<b>If the files were not sent, <code>check_send</b> will later on pick up here in the process</b>

	== Keeping Track under L10nStreamlining ==		== Keeping Track under L10nStreamlining ==