Globalyzer Lite for Continuous Globalization

Introduction

Globalyzer Lite can be deployed on a Continuous Globalization system. It allows i18n scanning of a project based on a Globalyzer project definition xml file saved filed most likely 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 at the top level directory which specifies how the code should be scanned.

Note: If you add LRM to this picture, the Continuous Globalization system needs to be a Linux machine, preferably Ubuntu.

Typical Workflow

Jenkins uses Globalyzer Lite via scripts to:

• Get the code to be analyzed from a repository
• Use the Globalyzer 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 project definition xml to have been created.