Lingoport CI/CD Trial - Revision history

Olibouban at 23:07, 22 August 2019

2019-08-22T23:07:51Z

← Older revision		Revision as of 23:07, 22 August 2019
Line 1:		Line 1:
	When a customer would like to check out the Lingoport products, it is recommended to set up a trial system.		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.		'''Please contact ''sales (at) lingoport.com''''' if that's the case. This section describes the process for a Lingoport CI/CD Trial.

Olibouban: /* The typical trial workflow */

2019-08-22T22:20:18Z

The typical trial workflow

← Older revision		Revision as of 22:20, 22 August 2019
Line 26:		Line 26:
	* Or provide a zip files over Secure FTP to an SFTP account provided by Lingoport		* Or provide a zip files over Secure FTP to an SFTP account provided by Lingoport

	==The ~~typical~~ trial ~~workflow~~==		==The trial ==
	# Lingoport sets up a dedicated CI/CD system for your company. Only Lingoport and your company has access to it (see [[AWS Security]] )		# Lingoport sets up a dedicated CI/CD system for your company. Only Lingoport and your company has access to it (see [[AWS Security]] )
	# Code is committed to a central source code repository (Git, Subversion, etc) by developers or sent via SFTP		# Code is committed to a central source code repository (Git, Subversion, etc) by developers or sent via SFTP

Olibouban: /* A typical workflow */

2019-08-22T22:20:05Z

A typical workflow

← Older revision		Revision as of 22:20, 22 August 2019
Line 26:		Line 26:
	* Or provide a zip files over Secure FTP to an SFTP account provided by Lingoport		* Or provide a zip files over Secure FTP to an SFTP account provided by Lingoport

	==A typical workflow==		==The typical trial workflow==
			# Lingoport sets up a dedicated CI/CD system for your company. Only Lingoport and your company has access to it (see [[AWS Security]] )
	# Code is committed to a central source code repository (Git, Subversion, etc) by developers or sent via SFTP		# Code is committed to a central source code repository (Git, Subversion, etc) by developers or sent via SFTP
	# The Lingoport CI/CD pulls the source code from the code repository and scan using Rule Sets stored on the Globalyzer Server or analyze the resource files.		# The Lingoport CI/CD pulls the source code from the code repository and scan using Rule Sets stored on the Globalyzer Server or analyze the resource files.
Line 32:		Line 33:
	# Emails are sent to designated recipients about the status of the translation upload or import.		# Emails are sent to designated recipients about the status of the translation upload or import.
	# Lingoport Dashboard updates the status using the results of the Globalyzer scans and LRM resource reports.		# Lingoport Dashboard updates the status using the results of the Globalyzer scans and LRM resource reports.
			# Lingoport demonstrates the system over a Web conference call.

Olibouban at 22:17, 22 August 2019

2019-08-22T22:17:09Z

← Older revision		Revision as of 22:17, 22 August 2019
Line 7:		Line 7:

	Note: For a step by step overview of security on the system, please refer to [[AWS Security]]		Note: For a step by step overview of security on the system, please refer to [[AWS Security]]

			== What Lingoport needs ==
			In order to provide some results on the type of files with which your organization works, Lingoport needs:
			* For Globalyzer i18n issues scanning
			** Some subset of your source code, in particular representative of user facing code
			** Typically around 50,000 lines of code

			* For LRM Resource Files analysis
			** Some representative subset of the resource files file format
			** The directory structure where the resource files are located, for files to be translated and some translated files.
			** The exact file names for files to be translated and some translated files as stored in the source code repository
			** The exact file structure with content for files to be translated and some translated files as stored in the source code repository

			There are two main alternatives to provide the files:
			* Provide access to a trial repository on the customer network
			** Repository URL, Account/Credentials, anything to connect to the trial repository

			* Or provide a zip files over Secure FTP to an SFTP account provided by Lingoport

	==A typical workflow==		==A typical workflow==
	# Code is committed to a central source code repository (Git, Subversion, etc) by developers.		# Code is committed to a central source code repository (Git, Subversion, etc) by developers or sent via SFTP
	# ~~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.		# The Lingoport CI/CD pulls the source code from the code repository and scan using Rule Sets stored on the Globalyzer Server or analyze the resource files.
	# ~~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~~.		# The Lingoport CI/CD determine if the resource files need to be sent to, or imported from, the translation vendor.
	# Emails are sent to designated recipients about the status of the translation upload or import.		# Emails are sent to designated recipients about the status of the translation upload or import.
	# Lingoport Dashboard updates the status using the results of the Globalyzer scans and LRM resource reports.		# Lingoport Dashboard updates the status using the results of the Globalyzer scans and LRM resource reports.

Olibouban at 22:06, 22 August 2019

2019-08-22T22:06:22Z

← Older revision		Revision as of 22:06, 22 August 2019
Line 5:		Line 5:

	[[File:Trial CICD.png\|500px]]		[[File:Trial CICD.png\|500px]]

			Note: For a step by step overview of security on the system, please refer to [[AWS Security]]

	==A typical workflow==		==A typical workflow==

Olibouban at 22:01, 22 August 2019

2019-08-22T22:01:35Z

← Older revision		Revision as of 22:01, 22 August 2019
Line 4:		Line 4:


	[File:Trial CICD.png]		[[File:Trial CICD.png\|500px]]

	==A typical workflow==		==A typical workflow==

Olibouban: /* A typical workflow */

2019-08-22T21:49:32Z

A typical workflow

← Older revision		Revision as of 21:49, 22 August 2019
Line 3:		Line 3:



			[File:Trial CICD.png]

	==A typical workflow==		==A typical workflow==

Olibouban: 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..."

2019-08-22T21:38:20Z

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..."

New page

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==
# Code is committed to a central source code repository (Git, Subversion, etc) by developers.
# 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.
# 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.
# Emails are sent to designated recipients about the status of the translation upload or import.
# Lingoport Dashboard updates the status using the results of the Globalyzer scans and LRM resource reports.