Difference between revisions of "On-Boarding New Projects"
(Created page with "This quick reference provides the main points to on-board a Globalyzer Lite and/or an LRM project using Jenkins. = Copy a Project in the Automation Tab = The simplest way to o...") |
|||
| (54 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | '''[OBSOLETE]''' |
||
| − | This quick reference provides the main points to on-board a Globalyzer Lite and/or an LRM project using Jenkins. |
||
| + | |||
| − | = Copy a Project in the Automation Tab = |
||
| + | |||
| − | The simplest way to on-board a new project is to simply copy an existing one and modify some attributes. The Template tab has a number of project to start with for the first time around. |
||
| + | '''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 [[Terms_and_Definitions#AutomationJob|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 [[Terms_and_Definitions#TMS|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. |
||
| − | * Go to the Automation Tab |
||
| + | |||
| − | * Copy a project: |
||
| + | [[File:JenkinsWWE.png|800px]] |
||
| − | ** Click on New Item |
||
| + | |||
| − | ** Enter a name in the form <Group_Name>.<Project_Name> in the <code>Enter an item name</code> text field at the top. The group is licensed and provided by Lingoport support. For instance, if you have a licensed group called <code>Acme</code>, the name to enter would be something like <code>Acme.Widget</code>. See [[On Boarding the Group License Expiration Job]] for more on the Group. It's recommended to use a licensed group even for Globalyzer Lite only project in case you want to add LRM in the future. |
||
| + | |||
| − | ** Enter the name of an existing Automation or Template Jenkins job in the <code>Copy from</code> text field at the bottom. If you copy from a Template, you have three possibilities: |
||
| + | After the Jenkins job completes, the Lingoport Dashboard is populated and for this project it looks like: |
||
| − | *** Lingoport.SampleLite |
||
| + | |||
| − | *** Lingoport.SampleLRM |
||
| + | [[File:DashboardWWE.png|800px]] |
||
| − | *** Lingoport.SampleLITELRM |
||
| + | * 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. |
||
| + | |||
| + | |||
| + | *[[On Boarding Overview | On Boarding Overview (an introduction to Jenkins and Lingoport)]] |
||
| + | *[[On Boarding a Localyzer Project]] |
||
| + | *[[On Boarding a Globalyzer Project]] |
||
| + | *[[On Boarding a project with both LRM and Globalyzer]] |
||
| + | |||
| + | Once Localyzer jobs have been on boarded, there are a couple of other jobs that can be set up. |
||
| + | *[[On Boarding the Nightly Job]] |
||
| + | *[[On Boarding the Prep Kit Job]] |
||
Latest revision as of 17:21, 20 March 2024
[OBSOLETE]
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.
After the Jenkins job completes, the Lingoport Dashboard is populated and for this project it looks like:
- 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.
- On Boarding Overview (an introduction to Jenkins and Lingoport)
- On Boarding a Localyzer Project
- On Boarding a Globalyzer Project
- On Boarding a project with both LRM and Globalyzer
Once Localyzer jobs have been on boarded, there are a couple of other jobs that can be set up.
