On Boarding the Prep Kit Job

OBSOLETE

The Prep Kit job is relevant only to projects that use Localyzer, it is not needed for Globalyzer-only analysis. The Prep Kit job is not neccessary. Prep kits can be triggered for a project from the Dashboard "Send to translate" button.

Project Nightly Steps

• Go to the 3 - Prep Kit tab
• Click New Item and give the job a name. A recommended job name is groupname.projectname-PrepKit, for instance 'Lingoport.javademo-PrepKit';
• Click Copy from and enter the name of an existing job, for instance Lingoport.SampleLRM-PrepKit
• Enable the job if it is not already.
• Only Prep the kit if necessary. At this point, it will send the files to be translated to the actual translation tool or FTP.
• Verify by clicking the Build Now button.
• Check the Jenkins console output for errors.
• There should be emails for each locale and "Upload Success"
• Check the Dashboard. There should be nothing under "Next Prep Kit Content" and the "Prep Kit Due Dates" should show today as the "Sent Date"
• Check that the prepkits were sent as expected.

Note: You will need to configure Localyzer to work with your L10n Vendor. Please see the L10n Vendors page for details.