Globalyzer Lite for Continuous Globalization
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.
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.
- 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
- 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.
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).