Difference between revisions of "On Boarding a Globalyzer Project"
(Created page with "=Before On Boarding a Globalyzer Project = To on-board any project, a number of basic information is needed: === Globalyzer and LRM === * '''Code Repository Location''' **...") |
|||
| Line 2: | Line 2: | ||
To on-board any project, a number of basic information is needed: |
To on-board any project, a number of basic information is needed: |
||
| − | === |
+ | === Code Repository Location === |
| + | * The code repository location and branch for the project. |
||
| − | * '''Code Repository Location''' |
||
| − | + | * Git locations could look like: https://github.com/group/project ; In addition, the branch for the Git project is needed |
|
| − | + | * SVN locations could look like: https://svn.group.com/project/trunk |
|
| + | * <b>Read and Write Access</b> granted to repository |
||
| − | *** SVN locations could look like: https://svn.group.com/project/trunk |
||
| − | ** <b>Read and Write Access</b> granted to repository |
||
| − | === |
+ | === Globalyzer Scan Information === |
| + | * The directories and files to be scanned |
||
| − | * '''Users''' |
||
| + | * The rulesets to be used to scan the source code. |
||
| − | ** The list of translation requesters. Those members to add to Jenkins so they have permission to trigger the Prep Kit job: <code> username1@company.org, username2@companyname.com </code> |
||
| − | ** The list of emails to be notified of the LRM actions: <code> username1@company.org, username2@companyname.com, username3@companyname.com </code> Note: All emails will also be used as Dashboard user identifiers. |
||
| + | =On Boarding the Automation Job= |
||
| − | * '''Locales''' |
||
| − | ** The locale of the files created by developers and to be translated |
||
| − | ** The list of target translation locales |
||
| − | ** The pseudo-locale |
||
| − | |||
| − | * '''Resource Files''' |
||
| − | ** Files types (for instance .properties, .resx, etc.) |
||
| − | ** Naming convention for the base file: for instance '''<filename>_en.properties''' or '''<filename>.properties''' |
||
| − | ** Translated file naming convention: for instance '''<filename>_fr_FR.properties''' |
||
| − | ** The files or directories which follow the above convention but should NOT be translated. For instance **/config*.properties |
||
| − | |||
| − | === Globalyzer === |
||
| − | |||
| − | * '''Globalyzer Scan Information''' |
||
| − | ** The directories files to be scanned |
||
| − | ** The rulesets to be used to scan the source code. |
||
| − | |||
| − | |||
| − | == Next Step == |
||
| − | [[On Boarding the Automation Job]] |
||
Revision as of 22:05, 10 December 2019
Contents
Before On Boarding a Globalyzer Project
To on-board any project, a number of basic information is needed:
Code Repository Location
- The code repository location and branch for the project.
- Git locations could look like: https://github.com/group/project ; In addition, the branch for the Git project is needed
- SVN locations could look like: https://svn.group.com/project/trunk
- Read and Write Access granted to repository
Globalyzer Scan Information
- The directories and files to be scanned
- The rulesets to be used to scan the source code.
