Difference between revisions of "On Boarding a project with both LRM and Globalyzer"
(Created page with "= Before On Boarding a project with LRM and Globalyzer = To on-board any project, a number of basic information is needed: === Globalyzer and LRM === * '''Code Repository Lo...") |
|||
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 === |
− | * '''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 |
||
− | ** <b>Read and Write Access</b> granted to repository |
||
+ | * The code repository location and branch for the project. |
||
− | === LRM === |
||
+ | ** 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 |
||
− | + | === Users === |
|
− | ** 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. |
||
+ | * 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> |
||
− | * '''Locales''' |
||
+ | * 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. |
||
− | ** The locale of the files created by developers and to be translated |
||
− | ** The list of target translation locales |
||
− | ** The pseudo-locale |
||
+ | === Locales === |
||
− | * '''Resource Files''' |
||
+ | * The locale of the files created by developers and to be translated |
||
− | ** Files types (for instance .properties, .resx, etc.) |
||
+ | * The list of target translation locales |
||
− | ** Naming convention for the base file: for instance '''<filename>_en.properties''' or '''<filename>.properties''' |
||
+ | * The pseudo-locale |
||
− | ** 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 |
||
− | === |
+ | === Resource File Types == |
+ | * 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 Scan Information === |
|
− | ** The directories files to be scanned |
||
− | ** The rulesets to be used to scan the source code. |
||
+ | * The directories files to be scanned |
||
+ | * The rulesets to be used to scan the source code. |
||
+ | * A Globalyzer Project file must be created with this information and placed in the code repository |
||
+ | =On Boarding the LRM and Globalyzer Automation Job= |
||
− | == Next Step == |
||
− | [[On Boarding the Automation Job]] |
Revision as of 22:20, 10 December 2019
Contents
Before On Boarding a project with LRM and Globalyzer
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
Users
- The list of translation requesters. Those members to add to Jenkins so they have permission to trigger the Prep Kit job:
username1@company.org, username2@companyname.com
- The list of emails to be notified of the LRM actions:
username1@company.org, username2@companyname.com, username3@companyname.com
Note: All emails will also be used as Dashboard user identifiers.
Locales
- The locale of the files created by developers and to be translated
- The list of target translation locales
- The pseudo-locale
= Resource File Types
- 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 Scan Information
- The directories files to be scanned
- The rulesets to be used to scan the source code.
- A Globalyzer Project file must be created with this information and placed in the code repository