Difference between revisions of "On-Boarding New Projects"

From Lingoport Wiki
Jump to: navigation, search
Line 15: Line 15:
   
 
*[[On Boarding Overview | On Boarding Overview (an introduction to Jenkins and Lingoport)]]
 
*[[On Boarding Overview | On Boarding Overview (an introduction to Jenkins and Lingoport)]]
*[[On Boarding an LRM Project]]
+
*[[On Boarding a Localyzer Project]]
 
*[[On Boarding a Globalyzer Project]]
 
*[[On Boarding a Globalyzer Project]]
 
*[[On Boarding a project with both LRM and Globalyzer]]
 
*[[On Boarding a project with both LRM and Globalyzer]]

Revision as of 20:23, 23 February 2021

On boarding is the process of creating Lingoport projects in Jenkins so that their status can be monitored in the Dashbaord. When the Jenkins job (called the automation job) runs, it checks out the code in the repository for scanning by Globalyzer and notes changes in the resource files that need to be sent to the translation management systems. For example for a project called CET.WorldWindExplorer, in Jenkins, the project is created and the Jenkins job runs successfully, as noted by the blue sphere.

JenkinsWWE.png


After the Jenkins job completes, the Lingoport Dashboard is populated and for this project it looks like:

DashboardWWE.png

  • This job is using both Localyzer to manage resource files and Globalyzer to scan the code for other issues.
  • There are 4 target locales and they are 100% translated.
  • There was 1 file with 2934 words that was translated into the four languages.
  • The Globalyzer scan found a number of internationalization issues that will need to be addressed.
  • Both Localyzer and Globalyzer are licensed and Localyzer can have up to 1000 projects in its CET group.


Once Localyzer jobs have been on boarded, there are a couple of other jobs that can be set up.