Localyzer Jenkins Jobs

LRM Jenkins Jobs are setup under 4 tabs:

• The '0 - infrastructure' tab contains Jenkins job which run independently of particular projects.
• The '1 - Automation' tab contains on-boarded jobs which generate the status of the project and pushes it to the dashboard, and pseudo-localizes resource files if necessary. These jobs tend to run whenever files are pushed to the repository for the project.
• The '2 - Nightlies' tab contains on-boarded jobs which run every day or every night and provide an update to the dashboard and an email to a set of recipients based on the configured frequency.
• The '3- PrepKit' tab contains on-boarded jobs which are triggered by a human intervention to send the kits for translation based on the configured translation endpoint.

We focus on the infrastructure jobs

Infrastructure Tab Jobs

• checksend: This job sweeps through unsent prep kits and tries to send them again to the configured translation endpoint, such as Lingotek, FTP, or WorldServer. It is best to keep this job triggered by a manual click so that the error is first corrected (translation group network access or authorization, etc.) before trying to resend the prep kit.
• debug: This job is a free type of job setup to enter any kind of command to debug the installation or anything else in the system.

Lingotek Jobs

• lingotekcallback: This job is invoked by Lingotek upon the last step of the workflow. Files are downloaded to the staging area and ready to be imported.
• LingotekCheckCallback: This job makes sure that files which needed to be downloaded from Lingotek have been downloaded and moved to the staging area
• LingotekImportKit: This job runs based on a frequency (every 2 hours) and runs the import for Lingotek files stashed under the staging area.