Advanced Localyzer Features - Revision history

Olibouban: Olibouban moved page Advanced LRM Features to Advanced Localyzer Features

2021-07-12T14:15:05Z

Olibouban moved page Advanced LRM Features to Advanced Localyzer Features

← Older revision	Revision as of 14:15, 12 July 2021
(No difference)

Rdaly at 22:32, 9 July 2021

2021-07-09T22:32:15Z

← Older revision		Revision as of 22:32, 9 July 2021
Line 15:		Line 15:

	= More Advanced Features=		= More Advanced Features=
	When setting up ~~LRM~~ on your system, a number of Jenkins jobs can then be created as per the on-boarding and take advantage of the out of the box functionality.		When setting up Localyzer on your system, a number of Jenkins jobs can then be created as per the on-boarding and take advantage of the out of the box functionality.
	The list of advanced features is available for ~~LRM~~ knowledgeable users.		The list of advanced features is available for Localyzer knowledgeable users.
	== Cherry Picker ==		== Cherry Picker ==
	[[Cherry Picker \| Cherry Picker]]		[[Cherry Picker \| Cherry Picker]]

	== Custom Tasks ==		== Custom Tasks ==
	Custom Tasks allow a developer to add functionality at certain stages of the ~~LRM~~ pipeline. For instance, before a kit is sent to translation, one may want to add some specific task. This requires knowledge of Java development.		Custom Tasks allow a developer to add functionality at certain stages of the Localyzer pipeline. For instance, before a kit is sent to translation, one may want to add some specific task. This requires knowledge of Java development.
	See [[Custom Tasks \| Custom Tasks]]		See [[Custom Tasks \| Custom Tasks]]

Rdaly at 21:28, 27 June 2019

2019-06-27T21:28:39Z

← Older revision		Revision as of 21:28, 27 June 2019
Line 13:		Line 13:

	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.

			= More Advanced Features=
			When setting up LRM on your system, a number of Jenkins jobs can then be created as per the on-boarding and take advantage of the out of the box functionality.
			The list of advanced features is available for LRM knowledgeable users.
			== Cherry Picker ==
			[[Cherry Picker \| Cherry Picker]]

			== Custom Tasks ==
			Custom Tasks allow a developer to add functionality at certain stages of the LRM pipeline. For instance, before a kit is sent to translation, one may want to add some specific task. This requires knowledge of Java development.
			See [[Custom Tasks \| Custom Tasks]]

Rdaly: Created page with "= How do I call a Jenkins job remotely? = One possible way to call a Jenkins job remotely is to use cURL. For instance, curl "/view/Infrastructure/job/LRMCri..."

2019-06-27T21:25:08Z

Created page with "= How do I call a Jenkins job remotely? = One possible way to call a Jenkins job remotely is to use cURL. For instance, curl "<JENKINS_URL>/view/Infrastructure/job/LRMCri..."

New page

= How do I call a Jenkins job remotely? =

One possible way to call a Jenkins job remotely is to use cURL. For instance,

curl "<JENKINS_URL>/view/Infrastructure/job/LRMCriticalErrors/buildWithParameters?token=LGCRITICAL&SRC_PROJECT=Acme.Weather&BRANCH_NAME=test"

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

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.