LRM How do I - Revision history

Llawson: /* How do I configure a LRM project? */

2019-06-03T18:50:57Z

How do I configure a LRM project?

← Older revision		Revision as of 18:50, 3 June 2019
Line 59:		Line 59:
	= Project Definition =		= Project Definition =
	=== How do I configure a LRM project? ===		=== How do I configure a LRM project? ===
	~~See [[You may need to edit your project definition.~~ See [[Supported_Resource_Bundles#Lingoport_Resource_Manager_Configuration\|Project Definition]] for information about configuring a LRM project.		See [[Supported_Resource_Bundles#Lingoport_Resource_Manager_Configuration\|Project Definition]] for information about configuring a LRM project.

	= Reports =		= Reports =

Llawson: /* L10n Vendors */

2019-04-23T21:03:53Z

L10n Vendors

← Older revision		Revision as of 21:03, 23 April 2019
Line 13:		Line 13:

	See [[L10n_Vendors\| Translation Vendors]] for more information.		See [[L10n_Vendors\| Translation Vendors]] for more information.

			=== How do I setup an InContext Server for my project's translation vendor? ===
			See [[L10n_Vendors#InContext_Server_Configuration\|InContext Server Configuration]] for more information.

	== FTP ==		== FTP ==

Llawson: /* How do I send reports to a different location? */

2018-12-04T18:58:51Z

How do I send reports to a different location?

← Older revision		Revision as of 18:58, 4 December 2018
Line 60:		Line 60:
	= Reports =		= Reports =
	=== How do I send reports to a different location? ===		=== How do I send reports to a different location? ===
	Use option ''-f <report path>'' to send the report to a different report location.		Use option ''-f <report path>'' to send the report to a different report location. See [[LRM_Commands_Reference#Create_reports\|Create Reports]] for additional information.

	= How do I call an LRM job remotely? =		= How do I call an LRM job remotely? =

Llawson: /* Project Definition */

2018-12-04T18:56:43Z

Project Definition

← Older revision		Revision as of 18:56, 4 December 2018
Line 57:		Line 57:
	=== How do I configure a LRM project? ===		=== How do I configure a LRM project? ===
	See [[You may need to edit your project definition. See [[Supported_Resource_Bundles#Lingoport_Resource_Manager_Configuration\|Project Definition]] for information about configuring a LRM project.		See [[You may need to edit your project definition. See [[Supported_Resource_Bundles#Lingoport_Resource_Manager_Configuration\|Project Definition]] for information about configuring a LRM project.

			= Reports =
			=== How do I send reports to a different location? ===
			Use option ''-f <report path>'' to send the report to a different report location.

	= How do I call an LRM job remotely? =		= How do I call an LRM job remotely? =

Olibouban: /* Calling from Remote / cURL */

2018-06-14T20:19:27Z

Calling from Remote / cURL

← Older revision		Revision as of 20:19, 14 June 2018
Line 62:		Line 62:
	One possible way to call a Jenkins job remotely is to use cURL. For instance,		One possible way to call a Jenkins job remotely is to use cURL. For instance,

	curl "<JENKINS_URL>~~/jenkins~~/view/Infrastructure/job/LRMCriticalErrors/buildWithParameters?token=LGCRITICAL&SRC_PROJECT=CET.Smoke&BRANCH_NAME=MysterO"		curl "<JENKINS_URL>/view/Infrastructure/job/LRMCriticalErrors/buildWithParameters?token=LGCRITICAL&SRC_PROJECT=CET.Smoke&BRANCH_NAME=MysterO"

	will invoke the 'LRMCriticalErrors', a job that checks for critical errors on resource files handled by an LRM project, here 'CET.Smoke', for a given branch, here 'MysterO'.		will invoke the 'LRMCriticalErrors', a job that checks for critical errors on resource files handled by an LRM project, here 'CET.Smoke', for a given branch, here 'MysterO'.

			If you want to get the console output, use the following command after the previous one:

			curl -X POST "<JENKINS_URL>/view/Infrastructure/job/LRMCriticalErrors/lastBuild/consoleText"


	To be called remotely, a Jenkins job must be configured with a token for the 'Build Trigger Remotely' build trigger, like LGCRITICAL for LRMCriticalErrors.		To be called remotely, a Jenkins job must be configured with a token for the 'Build Trigger Remotely' build trigger, like LGCRITICAL for LRMCriticalErrors.

Olibouban: /* Calling from Remote / cURL */

2018-06-14T20:00:57Z

Calling from Remote / cURL

← Older revision		Revision as of 20:00, 14 June 2018
Line 65:		Line 65:

	will invoke the 'LRMCriticalErrors', a job that checks for critical errors on resource files handled by an LRM project, here 'CET.Smoke', for a given branch, here 'MysterO'.		will invoke the 'LRMCriticalErrors', a job that checks for critical errors on resource files handled by an LRM project, here 'CET.Smoke', for a given branch, here 'MysterO'.

			To be called remotely, a Jenkins job must be configured with a token for the 'Build Trigger Remotely' build trigger, like LGCRITICAL for LRMCriticalErrors.

	=== Calling from Remote / LingoBot CLI ===		=== Calling from Remote / LingoBot CLI ===

Olibouban: /* How do I call an LRM job remotely? */

2018-06-14T19:58:07Z

How do I call an LRM job remotely?

← Older revision		Revision as of 19:58, 14 June 2018
Line 59:		Line 59:

	= How do I call an LRM job remotely? =		= How do I call an LRM job remotely? =
	=== Calling from Remote / ~~ALM with~~ cURL ===		=== Calling from Remote / cURL ===
	One possible way to call a Jenkins job remotely is to use cURL. For instance,		One possible way to call a Jenkins job remotely is to use cURL. For instance,

Line 65:		Line 65:

	will invoke the 'LRMCriticalErrors', a job that checks for critical errors on resource files handled by an LRM project, here 'CET.Smoke', for a given branch, here 'MysterO'.		will invoke the 'LRMCriticalErrors', a job that checks for critical errors on resource files handled by an LRM project, here 'CET.Smoke', for a given branch, here 'MysterO'.

			=== Calling from Remote / LingoBot CLI ===
			LingoBot can be set up to be invoked either from a collaborative environment, such as Slack, or from a command line using lingobot-cli.jar.

			Some infrastructure Jenkins jobs can be invoked that way. (See java -jar lingobot-cli.jar). For instance, to check for LRM resource files critical errors, the same job as for the cURL invocation above, use this command

			java -jar lingobot-cli.jar "show errors" "CET.Smoke:MysterO"

Olibouban: /* Project Definition */

2018-06-14T19:52:36Z

Project Definition

← Older revision		Revision as of 19:52, 14 June 2018
Line 57:		Line 57:
	=== How do I configure a LRM project? ===		=== How do I configure a LRM project? ===
	See [[You may need to edit your project definition. See [[Supported_Resource_Bundles#Lingoport_Resource_Manager_Configuration\|Project Definition]] for information about configuring a LRM project.		See [[You may need to edit your project definition. See [[Supported_Resource_Bundles#Lingoport_Resource_Manager_Configuration\|Project Definition]] for information about configuring a LRM project.

			= How do I call an LRM job remotely? =
			=== Calling from Remote / ALM with cURL ===
			One possible way to call a Jenkins job remotely is to use cURL. For instance,

			curl "<JENKINS_URL>/jenkins/view/Infrastructure/job/LRMCriticalErrors/buildWithParameters?token=LGCRITICAL&SRC_PROJECT=CET.Smoke&BRANCH_NAME=MysterO"

			will invoke the 'LRMCriticalErrors', a job that checks for critical errors on resource files handled by an LRM project, here 'CET.Smoke', for a given branch, here 'MysterO'.

Llawson: /* How do I configure a LRM project */

2017-09-13T23:18:54Z

How do I configure a LRM project

← Older revision		Revision as of 23:18, 13 September 2017
Line 55:		Line 55:

	= Project Definition =		= Project Definition =
	=== How do I configure a LRM project ===		=== How do I configure a LRM project? ===
	See [[You may need to edit your project definition. See [[Supported_Resource_Bundles#Lingoport_Resource_Manager_Configuration\|Project Definition]] for information about configuring a LRM project.		See [[You may need to edit your project definition. See [[Supported_Resource_Bundles#Lingoport_Resource_Manager_Configuration\|Project Definition]] for information about configuring a LRM project.

Llawson: /* Prep Kit */

2017-09-13T23:18:42Z

Prep Kit

← Older revision		Revision as of 23:18, 13 September 2017
Line 53:		Line 53:
	* 0 - prep files are for full-file		* 0 - prep files are for full-file
	* 1 - prep files can be for changes-only		* 1 - prep files can be for changes-only

			= Project Definition =
			=== How do I configure a LRM project ===
			See [[You may need to edit your project definition. See [[Supported_Resource_Bundles#Lingoport_Resource_Manager_Configuration\|Project Definition]] for information about configuring a LRM project.