Difference between revisions of "Globalyzer CLI for Continuous Globalization"
(→Introduction) |
(→Target User) |
||
| Line 3: | Line 3: | ||
= Target User= |
= Target User= |
||
| − | The typical Globalyzer |
+ | The typical Globalyzer CLI user is a Jenkins system which automates the tasks of scanning and pushing the results to the Dashboard. |
= Typical Deployment = |
= Typical Deployment = |
||
Revision as of 20:02, 26 August 2015
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
Typical Workflow
The developer uses to Lite within the IDE to:
- Scan the code being worked on for potential i18n issues before checking in the code to the source code repository
- refactors the code based on the checks
- pushes that code to the repository
This requires the rule sets used to scan the code have been vetted and the Globalyzer project definition file makes sense.
