Importing Translated Kits

To import files from translation, a number of jobs are executed on Jenkins:

• Download Translations:
  • From Lingotek side: It uses the callback mechanism to let Jenkins know files are translation complete; Another job, LingotekDownload, uses that information to retrieve the files via the Lingotek API and move them to the staging area
  • From FTP: A timed Jenkins trigger looks for all the possible FTP locations and moves the files to the staging area
• Import from staging, the system checks the files under staging, 'import' them into the source directory at the right location, and invokes the right VCS type to push the files to the repository. This last step uses the config_vcs.properties file.
  • For Lingotek files, the Jenkins job LingotekImport is called
  • For FTP, the Jenkins job FTPImport is called.

The following sections details the locations of the files as they move through the system.

Lingotek

LingotekCallback

The LingotekCallback Jenkins job The first step is to collect the files from the source directly, after a clean checkout/clone from the repository. If all is copacetic, the files to be send for translation are moved under the core LRM data directory, LRM_DATA_HOME, which is typically set to ~/Lingoport_Data/LRM.

For instance, if this is the second prep kit, the base files would be moved under:

<group_name>
├── logs
├── prep_kit
│   └── <project>
│       └── PREP_KIT_2

Moving the Prep Kit under staging

If that stage is successful, the files are then getting ready to be sent and are placed under the sendkits/lingotek or sendkits/ftp depending on the project configuration:

staging
├── ...
├── sendkits
│   └── lingotek
│       ├── <group_name>
│       │   └── <project_name>
│               └── PREP_KIT_2
│                   ├── BaseFileSearch_fr.xml
│                   ├── FilesToPrep.xml
│                   ├── fr
│                   │   ├── file1_en.properties
│                   │   └── file2_en.properties
│                   ├── <project_name>_1_fr.xml
│                   └── IncompletePrepKit.xml

Sending the Files under staging

If this has been successful, the next step is to send the files to Lingotek or FTP, depending on the configuration. This may fail due to network problems, server saturation, or other causes. Until the files have successfully been sent, they are kept under staging.

If the files were not sent, check_send will later on pick up here in the process

Keeping Track under L10nStreamlining

L10nStreamlining helps keep track of what was sent and received. The last stage of the Prep Kit process is to move the files which were under

• ~/Lingoport_Data/LRM/staging/sendkits

over to

• ~/Lingoport_Data/L10nStreamlining/<group_name>/projects<project_name>/prepkits/PREP_KIT_2.