Globalyzer CLI for Continuous Globalization

From Lingoport Wiki
Revision as of 20:20, 26 August 2015 by Olibouban (talk | contribs) (→‎Typical Deployment)
Jump to: navigation, search

Introduction

Globalyzer CLI can be deployed on a Continuous Globalization system. It allows i18n scanning of a project based on a Globalyzer project.gproj saved filed most likely at the top level directory of the source code; the results are then pushed to the Dashboard.

Target User

The typical Globalyzer CLI user is a Jenkins system which automates the tasks of scanning and pushing the results to the Dashboard.

Typical Deployment

Lite has been unzipped on the software developer's desktop and configured as an external tool in their IDE. The source code has a Globalyzer project definition file at the top level directory which specifies how the code should be scanned. The developer's desktop has access to the Globalyzer server

CLI for CI.gif

Typical Workflow

Jenkins uses to Globalyzer CLI via scripts to:

  • Get the code to be analyzed from a repository
  • Import the Globalyzer project from the project.gproj file if necessary. (The project may already exist in the database)
  • Scan the code for potential i18n issues
  • Push the results of the scan to the Dashboard


This requires the rule sets used to scan the code have been vetted and the Globalyzer project.gproj file makes sense.

Retrieved from "http://wiki.lingoport.com/index.php?title=Globalyzer_CLI_for_Continuous_Globalization&oldid=87308"