Difference between revisions of "LRM for Continuous Globalization"

From Lingoport Wiki
Jump to: navigation, search
(Introduction)
(Target User)
Line 5: Line 5:
   
 
= Target User=
 
= Target User=
The results are presented via the Dashboard for any registered users, such as development team members, development management, i18n specialists, L10n management, translators, QA, etc.
+
The results are presented via the [[Terms_and_Definitions|Dashboard]] for any registered users, such as development team members, development management, i18n specialists, L10n management, translators, QA, etc.
 
 
The typical LRM <code>actor</code> is a Jenkins system which automates the different tasks and pushes the results to the Dashboard.
+
The typical [[Terms_and_Definitions|LRM]] <code>actor</code> is a [[Terms_and_Definitions|Jenkins]] system which automates the different tasks and pushes the results to the Dashboard.
   
 
= Typical Deployment =
 
= Typical Deployment =

Revision as of 21:01, 22 December 2016

Introduction

The Lingoport Resource Manager, or LRM, is designed to be deployed on a Continuous Globalization system. It automates the tasks for tracking, checking, sending, receiving, and pushing/checking resource bundles to a repository, and provides an accurate translation status from the Dashboard's code perspective.

It integrates seamlessly with translation products, such as Lingotek.

Target User

The results are presented via the Dashboard for any registered users, such as development team members, development management, i18n specialists, L10n management, translators, QA, etc.

The typical LRM actor is a Jenkins system which automates the different tasks and pushes the results to the Dashboard.

Typical Deployment

LRM is installed on the Continuous Globalization system, with a database to track the actions and the status of the resource bundles. The LRM project has been on-boarded on the Continuous Globalization system.

LRM for CI2.gif

Note: the Continuous Globalization system needs to be a Linux machine, preferably Ubuntu.

Typical Workflow

Jenkins uses LRM via scripts to:

  • Get the code from a repository
  • Establish the status of the translation for all resource bundles
  • Push prep kits to translation products if necessary and if the critical checks pass.
  • Pull translated files from the translation products if necessary
  • Check the translated files and push them to the repository at the right location if the critical checks pass
  • Notify the configured recipients of the actions taken

Installation Notes

Setting up LRM requires more in-depth installation and configuration than setting up the client side of Globalyzer. Please refer to this section for Installation and Configuration .