Difference between revisions of "TradosEnterprise"
(→Configure FTP) |
|||
| Line 70: | Line 70: | ||
</ul> |
</ul> |
||
<li> |
<li> |
||
| + | Set the FTP credentials in ~jenkins/.netrc, which must correspond to the <code>TRADOS_ENTERPRISE_FTP</code> value |
||
| − | Create an Trados Enterprise local vendor in Jenkins: |
||
</li> |
</li> |
||
<ul> |
<ul> |
||
| − | <li> |
+ | <li>machine <FTP DNS></li> |
| + | <li>login <user></li> |
||
| − | <li>Scroll down to the <b>LRM L10n Vendor Setup</b> section and select <b>Add Local Vendor</b></li> |
||
| − | <li> |
+ | <li>password <pwd></li> |
| − | <li>Select <b>Group</b> or <b>Project</b>; if group, select group name from drop down list</li> |
||
| − | <li>Configure Prep Kit Files Directory: <code>/var/lib/jenkins/translation/TradosEnterprise/to_translation</code></li> |
||
| − | <li>Configure Imported Files Directory:<code>/var/lib/jenkins/translation/TradosEnterprise/from_translation</code></li> |
||
| − | <li>Save</li> |
||
| − | </ul> |
||
| − | <li> |
||
| − | Configure your Jenkins job to use Trados Enterprise local vendor: |
||
| − | </li> |
||
| − | <ul> |
||
| − | <li>Select the Jenkins job you want to use Trados Enterprise</li> |
||
| − | <li>Click Configure</li> |
||
| − | <li>Scroll down to the <b>L10n Vendor</b> section of your LRM configuration</li> |
||
| − | <li>Choose <b>Group</b> or <b>Project</b>; if project, click <b>Local Vendor</b> and then select the <b>Local Vendor Name</b> from the list</li> |
||
| − | <li>Save</li> |
||
</ul> |
</ul> |
||
</ol> |
</ol> |
||
| − | |||
| − | |||
| − | |||
| − | machine centralftp.sdl.com |
||
| − | login Lingoport_US |
||
| − | password WnM7Bz |
||
Revision as of 19:34, 27 May 2022
Trados Enterprise uses FTP in order to pass files back and forth with Localyzer. However, because the structure on the FTP site for Trados Enterprise is organized by locale-named directories, the configuration to move files back and forth requires first a local vendor, which is then used by two Jenkins jobs, TradosEnterpriseUpload and TradosEnterpriseDownload to move files back and forth using FTP.
Contents
Link Localyzer and Trados Enterprise
Firstly, configure a Local Vendor.
To begin working with Trados Enterprise, create or use the following directories on the Linux file system:
/var/lib/jenkins/translation/TradosEnterprise/to_translation/var/lib/jenkins/translation/TradosEnterprise/from_translation- Create an Trados Enterprise local vendor in Jenkins:
- Select Manage Jenkins->Configure System
- Scroll down to the LRM L10n Vendor Setup section and select Add Local Vendor
- Provide a unique vendor name
- Select Group or Project; if group, select group name from drop down list
- Configure Prep Kit Files Directory:
/var/lib/jenkins/translation/TradosEnterprise/to_translation - Configure Imported Files Directory:
/var/lib/jenkins/translation/TradosEnterprise/from_translation - Save
- Configure your Jenkins job to use Trados Enterprise local vendor:
- Select the Jenkins job you want to use Trados Enterprise
- Click Configure
- Scroll down to the L10n Vendor section of your LRM configuration
- Choose Group or Project; if project, click Local Vendor and then select the Local Vendor Name from the list
- Save
Configure and Enable Trados Enterprise Jenkins Jobs
- Enable the TradosEnterpriseUpload Jenkins job.
- Enable the TradosEnterpriseDownload Jenkins job.
- Make sure the Jenkins job TradosEnterpriseUpload trigger Build after other projects are built after DashboardPrepkit.
- Modify the Jenkins job LocalVendorDownload and check Build after other projects are built and then in Projects to watch, type in TradosEnterpriseDownload.
Trados Enterprise Locale Mapping
Configure config_trados_enterprise_locale_mapping.properties (which can be specified at the group or project config level).
This file maps locales from LRM to Trados Enterprise. For example, LRM supports the language only locale fr, which must be mapped to fr-FR for Trados Enterprise.
# #Locale mapping language only repo locales <--> Trados Enterprise Locales aa=aa-DJ ab=ab-GE af=af-ZA ak=ak-GH am=am-ET ...
Configure FTP
- Set a Jenkins global variable:
- The name of the Jenkins variable must be:
TRADOS_ENTERPRISE_FTP - The value of the variable must be in the form:
ftp://<user>@<FTP DNS> -
Set the FTP credentials in ~jenkins/.netrc, which must correspond to the
TRADOS_ENTERPRISE_FTPvalue - machine <FTP DNS>
- login <user>
- password <pwd>
