Difference between revisions of "Globalyzer Lite for Continuous Globalization"
(→Installation Note) |
(→Installation Components) |
||
| (16 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Introduction = |
= Introduction = |
||
| − | Globalyzer Lite can be deployed on a Continuous Globalization system. It enables i18n scanning of a project based on a Globalyzer project definition xml file, most likely saved at the top level directory of the source code; the results are then pushed to the Dashboard. |
+ | [[Terms_and_Definitions#GlobalyzerLite|Globalyzer Lite]] can be deployed on a [[Terms_and_Definitions#ContinuousGlobalization|Continuous Globalization]] system. It enables [[Terms_and_Definitions#i18n|i18n]] [[Terms_and_Definitions#scan|scanning]] of a project based on a [[Terms_and_Definitions#Globalyzerproject|Globalyzer project definition xml file]], most likely saved at the top level directory of the source code; the results are then pushed to the [[Terms_and_Definitions#Dashboard|Dashboard]]. |
= 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|Dashboard]] for any registered users, such as development team members, development management, [[Terms_and_Definitions#i18n|i18n]] specialists, [[Terms_and_Definitions#localization|L10n]] management, translators, QA, etc. |
| − | The typical Globalyzer Lite <code>actor</code> is a Jenkins system which automates the tasks of scanning and pushing the results to the Dashboard. |
+ | The typical [[Terms_and_Definitions#GlobalyzerLite|Globalyzer Lite]] <code>actor</code> is a [[Terms_and_Definitions#Jenkins|Jenkins]] system which automates the tasks of scanning and pushing the results to the [[Terms_and_Definitions#Dashboard|Dashboard]]. |
= Typical Deployment = |
= Typical Deployment = |
||
| − | Globalyzer Lite can be unzipped from Jenkins every time, for instance on a master/slave Jenkins system, or may have been unzipped/installed beforehand, without any database requirement. |
+ | [[Terms_and_Definitions#GlobalyzerLite|Globalyzer Lite]] can be unzipped from [[Terms_and_Definitions#Jenkins|Jenkins]] every time, for instance on a master/slave Jenkins system, or may have been unzipped/installed beforehand, without any database requirement. |
| − | The source code must have a <code>project definition xml file</code> which specifies how the code should be scanned. It is recommended that this be placed at the top level directory of the project. |
+ | The source code must have a <code>project definition xml file</code> which specifies how the code should be [[Terms_and_Definitions#scan|scanned]]. It is recommended that this be placed at the top level directory of the project. |
[[File:Lite for CI.gif]] |
[[File:Lite for CI.gif]] |
||
| − | <b>Note</b>: If you add LRM to this picture, the Continuous Globalization system needs to be a Linux machine, preferably |
+ | <b>Note</b>: If you add [[Terms_and_Definitions#LRM|LRM]] to this picture, the [[Terms_and_Definitions#ContinuousGlobalization|Continuous Globalization]] system needs to be a Linux machine, preferably CentOS. |
= Typical Workflow= |
= Typical Workflow= |
||
| − | Jenkins uses Globalyzer Lite via scripts to: |
+ | [[Terms_and_Definitions#Jenkins|Jenkins]] uses [[Terms_and_Definitions#GlobalyzerLite|Globalyzer Lite]] via scripts to: |
| − | * Get the code to be analyzed from a repository |
+ | * Get the code to be analyzed from a [[Terms_and_Definitions#repository|repository]] |
| − | * Use the Globalyzer project definition file to scan the code for potential i18n issues with Globalyzer Lite |
+ | * Use the [[Terms_and_Definitions#LiteProjectDefn|Globalyzer Lite project definition file]] to [[Terms_and_Definitions#scan|scan]] the code for potential [[Terms_and_Definitions#i18n|i18n]] issues with Globalyzer Lite |
| − | ** Optionally push the results of the scan to the Dashboard or use the results for other purposes |
+ | ** Optionally push the results of the scan to the [[Terms_and_Definitions#Dashboard|Dashboard]] or use the results for other purposes |
| − | This requires the rule sets used to scan the code have been vetted and the Globalyzer <code>project definition xml</code> to have been created. |
+ | This requires the [[Terms_and_Definitions#ruleset|rule sets]] used to [[Terms_and_Definitions#scan|scan]] the code have been vetted and the Globalyzer Lite <code>project definition xml</code> to have been created. |
| + | = Installation Components = |
||
| + | * The '''Globalyzer Server''' (Server system) is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server. |
||
| + | * The '''Dashboard System''' and '''Continuous Globalization System''' are shown installed on different machines, although they could be one machine installed with the [[Terms_and_Definitions#stackinstaller|Stack Installer]]. The [[Terms_and_Definitions#GlobalyzerLite|Globalyzer Lite]] client is installed on the [[Terms_and_Definitions#continuousglobalizationsystem|Continuous Globalization System]] to analyze code. |
||
| + | * The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine. |
||
= Installation Note = |
= Installation Note = |
||
To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script. |
To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script. |
||
| − | To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, using-globalyzer-lite.html. |
+ | To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required). |
Latest revision as of 20:54, 17 January 2017
Contents
Introduction
Globalyzer Lite can be deployed on a Continuous Globalization system. It enables i18n scanning of a project based on a Globalyzer project definition xml file, most likely saved at the top level directory of the source code; the results are then pushed to the Dashboard.
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 Globalyzer Lite actor is a Jenkins system which automates the tasks of scanning and pushing the results to the Dashboard.
Typical Deployment
Globalyzer Lite can be unzipped from Jenkins every time, for instance on a master/slave Jenkins system, or may have been unzipped/installed beforehand, without any database requirement.
The source code must have a project definition xml file which specifies how the code should be scanned. It is recommended that this be placed at the top level directory of the project.
Note: If you add LRM to this picture, the Continuous Globalization system needs to be a Linux machine, preferably CentOS.
Typical Workflow
Jenkins uses Globalyzer Lite via scripts to:
- Get the code to be analyzed from a repository
- Use the Globalyzer Lite project definition file to scan the code for potential i18n issues with Globalyzer Lite
- Optionally push the results of the scan to the Dashboard or use the results for other purposes
This requires the rule sets used to scan the code have been vetted and the Globalyzer Lite project definition xml to have been created.
Installation Components
- The Globalyzer Server (Server system) is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.
- The Dashboard System and Continuous Globalization System are shown installed on different machines, although they could be one machine installed with the Stack Installer. The Globalyzer Lite client is installed on the Continuous Globalization System to analyze code.
- The Developer Machine is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.
Installation Note
To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script. To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, using-globalyzer-lite.html (login is required).
