Lingoport CI/CD Trial

From Lingoport Wiki
Revision as of 21:38, 22 August 2019 by Olibouban (talk | contribs) (Created page with "When a customer would like to check out the Lingoport products, it is recommended to set up a trial system. Please contact ''sales (at) lingoport.com'' if that's the case. Th...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

When a customer would like to check out the Lingoport products, it is recommended to set up a trial system. Please contact sales (at) lingoport.com if that's the case. This section describes the process for a Lingoport CI/CD Trial.


A typical workflow

  1. Code is committed to a central source code repository (Git, Subversion, etc) by developers.
  2. Jenkins tools pull the source code from the code repository and scan using Rule Sets stored on the Globalyzer Server or analyze the resource files.
  3. Jenkins tools determine if the resource files need to be sent to, or imported from, the translation vendor. This may be done via an FTP connection.
  4. Emails are sent to designated recipients about the status of the translation upload or import.
  5. Lingoport Dashboard updates the status using the results of the Globalyzer scans and LRM resource reports.