LRM for Continuous Globalization - Revision history

Rdaly: /* Installation Components */

2016-12-30T19:02:37Z

Installation Components

← Older revision		Revision as of 19:02, 30 December 2016
Line 28:		Line 28:
	= Installation Components =		= Installation Components =

	* The '''Dashboard ~~Server~~''' and '''~~Build Server~~''' ~~(Continuous Globalization system)~~ is shown on different machines, although they could be one machine. The Build Server transfers [[Terms_and_Definitions#resourcefiles\|resource files]] to and from the [[Terms_and_Definitions#TMS\|Translation Management System]].		* The '''Dashboard System''' and '''Continuous Globalization system''' is shown on different machines, although they could be one machine. The Build Server transfers [[Terms_and_Definitions#resourcefiles\|resource files]] to and from the [[Terms_and_Definitions#TMS\|Translation Management System]].
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.
	* There is no '''Globalyzer Server''' or Globalyzer clients in this scenario.		* There is no '''Globalyzer Server''' or Globalyzer clients in this scenario.

Rdaly: /* Installation Components */

2016-12-29T21:31:19Z

Installation Components

← Older revision		Revision as of 21:31, 29 December 2016
Line 28:		Line 28:
	= Installation Components =		= Installation Components =

	* The '''Dashboard Server''' and '''Build Server''' (Continuous Globalization system) is shown on different machines, although they could be one machine. The Build Server ~~communicates with~~ the [[Terms_and_Definitions#TMS\|Translation Management System]].		* The '''Dashboard Server''' and '''Build Server''' (Continuous Globalization system) is shown on different machines, although they could be one machine. The Build Server transfers [[Terms_and_Definitions#resourcefiles\|resource files]] to and from the [[Terms_and_Definitions#TMS\|Translation Management System]].
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.
	* There is no '''Globalyzer Server''' or Globalyzer clients in this scenario.		* There is no '''Globalyzer Server''' or Globalyzer clients in this scenario.

Rdaly: /* Installation Components */

2016-12-29T21:29:56Z

Installation Components

← Older revision		Revision as of 21:29, 29 December 2016
Line 28:		Line 28:
	= Installation Components =		= Installation Components =

	* The '''Dashboard Server''' and '''Build Server''' is shown on different machines, although they could be one machine. The Build Server communicates with the		* The '''Dashboard Server''' and '''Build Server''' (Continuous Globalization system) is shown on different machines, although they could be one machine. The Build Server communicates with the [[Terms_and_Definitions#TMS\|Translation Management System]].
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.
	* There is no '''Globalyzer Server''' or Globalyzer clients in this scenario		* There is no '''Globalyzer Server''' or Globalyzer clients in this scenario.

	= Installation Notes =		= Installation Notes =
	Setting up LRM requires more in-depth installation and configuration than setting up the client side of Globalyzer.		Setting up LRM requires more in-depth installation and configuration than setting up the client side of Globalyzer.
	Please refer to this section for [[ Installation and Configuration \| Installation and Configuration ]].		Please refer to this section for [[ Installation and Configuration \| Installation and Configuration ]].

Rdaly: /* Installation Components */

2016-12-29T21:09:21Z

Installation Components

← Older revision		Revision as of 21:09, 29 December 2016
Line 28:		Line 28:
	= Installation Components =		= Installation Components =

	* The '''Dashboard Server''' and '''Build Server''' is shown on different machines, although they could be one machine. The		* The '''Dashboard Server''' and '''Build Server''' is shown on different machines, although they could be one machine. The Build Server communicates with the
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.
	* There is no '''Globalyzer Server''' or Globalyzer clients in this scenario		* There is no '''Globalyzer Server''' or Globalyzer clients in this scenario

Rdaly: /* Installation Components */

2016-12-29T21:03:14Z

Installation Components

← Older revision		Revision as of 21:03, 29 December 2016
Line 28:		Line 28:
	= Installation Components =		= Installation Components =

	* The '''Dashboard Server''' and '''Build Server''' is shown on different machines, although they could be one machine.		* The '''Dashboard Server''' and '''Build Server''' is shown on different machines, although they could be one machine. The
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.
	* There is no Globalyzer Server or Globalyzer clients in this ~~deployment~~		* There is no '''Globalyzer Server''' or Globalyzer clients in this scenario

	= Installation Notes =		= Installation Notes =
	Setting up LRM requires more in-depth installation and configuration than setting up the client side of Globalyzer.		Setting up LRM requires more in-depth installation and configuration than setting up the client side of Globalyzer.
	Please refer to this section for [[ Installation and Configuration \| Installation and Configuration ]].		Please refer to this section for [[ Installation and Configuration \| Installation and Configuration ]].

Rdaly: /* Installation Components */

2016-12-29T21:02:09Z

Installation Components

← Older revision		Revision as of 21:02, 29 December 2016
Line 27:		Line 27:

	= Installation Components =		= Installation Components =
	* The '''Globalyzer Server''' is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.
	* The '''Dashboard Server''' and '''Build Server''' is shown on different machines, although they could be one machine. ~~The Globalyzer CLI client is installed on the Build Server to analyze code.~~		* The '''Dashboard Server''' and '''Build Server''' is shown on different machines, although they could be one machine.
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.
			* There is no Globalyzer Server or Globalyzer clients in this deployment

	= Installation Notes =		= Installation Notes =
	Setting up LRM requires more in-depth installation and configuration than setting up the client side of Globalyzer.		Setting up LRM requires more in-depth installation and configuration than setting up the client side of Globalyzer.
	Please refer to this section for [[ Installation and Configuration \| Installation and Configuration ]].		Please refer to this section for [[ Installation and Configuration \| Installation and Configuration ]].

Rdaly at 21:00, 29 December 2016

2016-12-29T21:00:59Z

← Older revision		Revision as of 21:00, 29 December 2016
Line 25:		Line 25:
	* Check the translated files and push them to the repository at the right location if the critical checks pass		* Check the translated files and push them to the repository at the right location if the critical checks pass
	* Notify the configured recipients of the actions taken		* Notify the configured recipients of the actions taken

			= Installation Components =
			* The '''Globalyzer Server''' is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.
			* The '''Dashboard Server''' and '''Build Server''' is shown on different machines, although they could be one machine. The Globalyzer CLI client is installed on the Build Server to analyze code.
			* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.

	= Installation Notes =		= Installation Notes =
	Setting up LRM requires more in-depth installation and configuration than setting up the client side of Globalyzer.		Setting up LRM requires more in-depth installation and configuration than setting up the client side of Globalyzer.
	Please refer to this section for [[ Installation and Configuration \| Installation and Configuration ]].		Please refer to this section for [[ Installation and Configuration \| Installation and Configuration ]].

Rdaly at 22:02, 27 December 2016

2016-12-27T22:02:36Z

Rdaly: /* Typical Workflow */

2016-12-22T21:48:55Z

Typical Workflow

← Older revision		Revision as of 21:48, 22 December 2016
Line 18:		Line 18:

	= Typical Workflow=		= Typical Workflow=
	Jenkins uses LRM via scripts to:		[[Terms_and_Definitions\|Jenkins]] uses [[Terms_and_Definitions\|LRM]] via scripts to:
	* Get the code from a repository		* Get the code from a [[Terms_and_Definitions\|repository]]
	* Establish the status of the translation for all resource bundles		* Establish the status of the translation for all [[Terms_and_Definitions\|resource bundles]]
	* Push prep kits to translation products if necessary and if the critical checks pass.		* Push [[Terms_and_Definitions\|prep kits]] to translation products if necessary and if the critical checks pass.
	* Pull translated files from the translation products if necessary		* Pull translated files from the translation products if necessary
	* Check the translated files and push them to the repository at the right location if the critical checks pass		* Check the translated files and push them to the repository at the right location if the critical checks pass

Rdaly: /* Typical Deployment */

2016-12-22T21:43:59Z

Typical Deployment

← Older revision		Revision as of 21:43, 22 December 2016
Line 15:		Line 15:
	[[File:LRM for CI2.gif]]		[[File:LRM for CI2.gif]]

	<b>Note</b>: the Continuous Globalization system needs to be a Linux machine, preferably ~~Ubuntu~~.		<b>Note</b>: the Continuous Globalization system needs to be a Linux machine, preferably CentOS.

	= Typical Workflow=		= Typical Workflow=

← Older revision		Revision as of 22:02, 27 December 2016
Line 1:		Line 1:
	= Introduction =		= Introduction =
	The [[Terms_and_Definitions\|Lingoport Resource Manager]], or LRM, is designed to be deployed on a [[Terms_and_Definitions\|Continuous Globalization]] system. It automates the tasks for tracking, checking, sending, receiving, and pushing/checking [[Terms_and_Definitions\|resource ~~bundles~~]] to a [[Terms_and_Definitions\|repository]], and provides an accurate translation status from the Dashboard's code perspective.		The [[Terms_and_Definitions#LingoportResourceManager\|Lingoport Resource Manager]], or LRM, is designed to be deployed on a [[Terms_and_Definitions#ContinuousGlobalization\|Continuous Globalization]] system. It automates the tasks for tracking, checking, sending, receiving, and pushing/checking [[Terms_and_Definitions#resourcefiles\|resource files]] to a [[Terms_and_Definitions#repository\|repository]], and provides an accurate translation status from the Dashboard's code perspective.

	It integrates seamlessly with translation products, such as Lingotek.		It integrates seamlessly with translation products, such as Lingotek.

	= Target User=		= Target User=
	The results are presented via the [[Terms_and_Definitions\|Dashboard]] for any registered users, such as development team members, development management, i18n specialists, L10n management, translators, QA, etc.		The results are presented via the [[Terms_and_Definitions#Dashboard\|Dashboard]] for any registered users, such as development team members, development management, i18n specialists, L10n management, translators, QA, etc.

	The typical [[Terms_and_Definitions\|LRM]] <code>actor</code> is a [[Terms_and_Definitions\|Jenkins]] system which automates the different tasks and pushes the results to the Dashboard.		The typical [[Terms_and_Definitions#LRM\|LRM]] <code>actor</code> is a [[Terms_and_Definitions#Jenkins\|Jenkins]] system which automates the different tasks and pushes the results to the Dashboard.

	= Typical Deployment =		= Typical Deployment =
	[[Terms_and_Definitions\|LRM]] is installed on the [[Terms_and_Definitions\|Continuous Globalization]] system, with a database to track the actions and the status of the resource bundles.		[[Terms_and_Definitions#LRM\|LRM]] is installed on the [[Terms_and_Definitions#ContinuousGlobalization\|Continuous Globalization]] system, with a database to track the actions and the status of the resource bundles.
	The LRM project has been on-boarded on the Continuous Globalization system.		The LRM project has been on-boarded on the Continuous Globalization system.

Line 18:		Line 18:

	= Typical Workflow=		= Typical Workflow=
	[[Terms_and_Definitions\|Jenkins]] uses [[Terms_and_Definitions\|LRM]] via scripts to:		[[Terms_and_Definitions#Jenkins\|Jenkins]] uses [[Terms_and_Definitions#LRM\|LRM]] via scripts to:
	* Get the code from a [[Terms_and_Definitions\|repository]]		* Get the code from a [[Terms_and_Definitions#repository\|repository]]
	* Establish the status of the translation for all [[Terms_and_Definitions\|resource ~~bundles~~]]		* Establish the status of the translation for all [[Terms_and_Definitions#resourcefiles\|resource files]]
	* Push [[Terms_and_Definitions\|prep kits]] to translation products if necessary and if the critical checks pass.		* Push [[Terms_and_Definitions#prepkit\|prep kits]] to translation products if necessary and if the critical checks pass.
	* Pull translated files from the translation products if necessary		* Pull translated files from the translation products if necessary
	* Check the translated files and push them to the repository at the right location if the critical checks pass		* Check the translated files and push them to the repository at the right location if the critical checks pass