Globalyzer CLI for Continuous Globalization - Revision history

Rdaly: /* Installation Components */

2016-12-30T18:48:41Z

Installation Components

← Older revision		Revision as of 18:48, 30 December 2016
Line 27:		Line 27:
	= Installation Components =		= Installation Components =
	* The '''Globalyzer Server''' (System server) is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.		* The '''Globalyzer Server''' (System 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~~''' ~~(Continuous Globalization system)~~ 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 System''' and '''Continuous Globalization system''' is shown on different machines, although they could be one machine installed with the [[Terms_and_Definitions#stackinstaller\|Stack Installer]] The [[Terms_and_Definitions#GlobalyzerCLI\|Globalyzer CLI]] client is installed on the Continuous Globalization system 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.		* 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 =
	To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.		To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.

Rdaly: /* Installation Components */

2016-12-29T21:23:16Z

Installation Components

← Older revision		Revision as of 21:23, 29 December 2016
Line 26:		Line 26:

	= 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 '''Globalyzer Server''' (System 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''' (Continuous Globalization system) 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.		* 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 =
	To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.		To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.

Rdaly: /* Installation Components */

2016-12-29T20:55:27Z

Installation Components

← Older revision		Revision as of 20:55, 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 '''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''' ~~are installed~~ on different machines, although they could be one ~~machines~~. 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 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.		* 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 =
	To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.		To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.

Rdaly at 20:54, 29 December 2016

2016-12-29T20:54:49Z

← Older revision		Revision as of 20:54, 29 December 2016
Line 24:		Line 24:

	This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to scan the code have been vetted and the Globalyzer <code>project.gproj</code> file makes sense.		This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to scan the code have been vetted and the Globalyzer <code>project.gproj</code> file makes sense.

			= 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''' are installed on different machines, although they could be one machines. 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 =
	To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.		To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.

Rdaly at 21:58, 27 December 2016

2016-12-27T21:58:29Z

← Older revision		Revision as of 21:58, 27 December 2016
Line 1:		Line 1:
	= Introduction =		= Introduction =
	[[Terms_and_Definitions\|Globalyzer CLI]] can be deployed on a [[Terms_and_Definitions\|Continuous Globalization]] system. It enables [[Terms_and_Definitions\|i18n]] [[Terms_and_Definitions\|scanning]] of a project based on a Globalyzer <code>project.gproj</code> saved filed most likely at the top level directory of the source code; the results are then pushed to the [[Terms_and_Definitions\|Dashboard]].		[[Terms_and_Definitions#GlobalyzerCLI\|Globalyzer CLI]] can be deployed on a [[Terms_and_Definitions#ContinuousGlobalyization\|Continuous Globalization]] system. It enables [[Terms_and_Definitions#i18n\|i18n]] [[Terms_and_Definitions#scan\|scanning]] of a project based on a Globalyzer <code>project.gproj</code> saved filed most likely at the top level directory of the source code; the results are then pushed to the [[Terms_and_Definitions#Dashboard\|Dashboard]].

	= 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, [[Terms_and_Definitions\|i18n]] specialists, [[Terms_and_Definitions\|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, [[Terms_and_Definitions#i18n\|i18n]] specialists, [[Terms_and_Definitions#localization\|L10n]] management, translators, QA, etc.

	The typical [[Terms_and_Definitions\|Globalyzer CLI]] <code>actor</code>is a [[Terms_and_Definitions\|Jenkins]] system which automates the tasks of [[Terms_and_Definitions\|scanning]] and pushing the results to the Dashboard.		The typical [[Terms_and_Definitions#GlobalyzerCLI\|Globalyzer CLI]] <code>actor</code>is a [[Terms_and_Definitions#Jenkins\|Jenkins]] system which automates the tasks of [[Terms_and_Definitions#scan\|scanning]] and pushing the results to the Dashboard.

	= Typical Deployment =		= Typical Deployment =
	The Globalyzer client, including the Command Line Interface jar file, has been installed on the [[Terms_and_Definitions\|Continuous Globalization]] system, with a database to store the results of the scans.		The Globalyzer client, including the Command Line Interface jar file, has been installed on the [[Terms_and_Definitions#ContinuousGlobalization\|Continuous Globalization]] system, with a database to store the results of the scans.
	The source code may have a <code>project.gproj</code> file at the top level directory which specifies how the code should be scanned.		The source code may have a <code>project.gproj</code> file at the top level directory which specifies how the code should be scanned.

Line 16:		Line 16:

	= Typical Workflow=		= Typical Workflow=
	[[Terms_and_Definitions\|Jenkins]] uses the [[Terms_and_Definitions\|Globalyzer CLI]] via scripts to:		[[Terms_and_Definitions#Jenkins\|Jenkins]] uses the [[Terms_and_Definitions#GlobalyzerCLI\|Globalyzer CLI]] via scripts to:
	* Get the code to be analyzed from a [[Terms_and_Definitions\|repository]]		* Get the code to be analyzed from a [[Terms_and_Definitions#repository\|repository]]
	** Optionally, import the [[Terms_and_Definitions\|Globalyzer project]] from the <code>project.gproj</code> file <i>if necessary</i>; The project may already exist in the database.		** Optionally, import the [[Terms_and_Definitions#Globalyzerproject\|Globalyzer project]] from the <code>project.gproj</code> file <i>if necessary</i>; The project may already exist in the database.
	* Scan the code for potential [[Terms_and_Definitions\|i18n]] issues		* Scan the code for potential [[Terms_and_Definitions#i18n\|i18n]] issues
	* Push the results of the [[Terms_and_Definitions\|scan]] to the [[Terms_and_Definitions\|Dashboard]]		* Push the results of the [[Terms_and_Definitions#scan\|scan]] to the [[Terms_and_Definitions#Dashboard\|Dashboard]]


	This requires the [[Terms_and_Definitions\|rule sets]] used to scan the code have been vetted and the Globalyzer <code>project.gproj</code> file makes sense.		This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to scan the code have been vetted and the Globalyzer <code>project.gproj</code> file makes sense.

	= Installation Notes =		= Installation Notes =
	To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.		To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.

Rdaly: /* Typical Workflow */

2016-12-22T18:52:14Z

Typical Workflow

← Older revision		Revision as of 18:52, 22 December 2016
Line 16:		Line 16:

	= Typical Workflow=		= Typical Workflow=
	Jenkins uses the Globalyzer CLI via scripts to:		[[Terms_and_Definitions\|Jenkins]] uses the [[Terms_and_Definitions\|Globalyzer CLI]] via scripts to:
	* Get the code to be analyzed from a repository		* Get the code to be analyzed from a [[Terms_and_Definitions\|repository]]
	** Optionally, import the Globalyzer project from the <code>project.gproj</code> file <i>if necessary</i>; The project may already exist in the database.		** Optionally, import the [[Terms_and_Definitions\|Globalyzer project]] from the <code>project.gproj</code> file <i>if necessary</i>; The project may already exist in the database.
	* Scan the code for potential i18n issues		* Scan the code for potential [[Terms_and_Definitions\|i18n]] issues
	* Push the results of the scan to the Dashboard		* Push the results of the [[Terms_and_Definitions\|scan]] to the [[Terms_and_Definitions\|Dashboard]]


	This requires the rule sets used to scan the code have been vetted and the Globalyzer <code>project.gproj</code> file makes sense.		This requires the [[Terms_and_Definitions\|rule sets]] used to scan the code have been vetted and the Globalyzer <code>project.gproj</code> file makes sense.

	= Installation Notes =		= Installation Notes =
	To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.		To install the Command Line Interface client (CLI), login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer.

Rdaly: /* Typical Deployment */

2016-12-22T18:45:01Z

Typical Deployment

← Older revision		Revision as of 18:45, 22 December 2016
Line 8:		Line 8:

	= Typical Deployment =		= Typical Deployment =
	The Globalyzer client, including the Command Line Interface jar file, has been installed on the Continuous Globalization system, with a database to store the results of the scans.		The Globalyzer client, including the Command Line Interface jar file, has been installed on the [[Terms_and_Definitions\|Continuous Globalization]] system, with a database to store the results of the scans.
	The source code may have a <code>project.gproj</code> file at the top level directory which specifies how the code should be scanned.		The source code may have a <code>project.gproj</code> file at the top level directory which specifies how the code should be scanned.

Rdaly: /* Typical Deployment */

2016-12-22T18:43:28Z

Typical Deployment

← Older revision		Revision as of 18:43, 22 December 2016
Line 13:		Line 13:
	[[File:CLI for CI.gif]]		[[File:CLI for CI.gif]]

	<b>Note</b>: If you add LRM to this picture, the Continuous Globalization system needs to be a <b>Linux machine, preferably ~~Ubuntu~~</b>.		<b>Note</b>: If you add LRM to this picture, the Continuous Globalization system needs to be a <b>Linux machine, preferably CentOS</b>.

	= Typical Workflow=		= Typical Workflow=

Rdaly: /* Target User */

2016-12-22T18:10:30Z

Target User

← Older revision		Revision as of 18:10, 22 December 2016
Line 3:		Line 3:

	= Target User=		= Target User=
	The results are presented via the 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]] for any registered users, such as development team members, development management, [[Terms_and_Definitions\|i18n]] specialists, [[Terms_and_Definitions\|L10n]] management, translators, QA, etc.

	The typical Globalyzer CLI <code>actor</code>is a Jenkins system which automates the tasks of scanning and pushing the results to the Dashboard.		The typical [[Terms_and_Definitions\|Globalyzer CLI]] <code>actor</code>is a [[Terms_and_Definitions\|Jenkins]] system which automates the tasks of [[Terms_and_Definitions\|scanning]] and pushing the results to the Dashboard.

	= Typical Deployment =		= Typical Deployment =

Rdaly: /* Introduction */

2016-12-22T17:25:10Z

Introduction

← Older revision		Revision as of 17:25, 22 December 2016
Line 1:		Line 1:
	= Introduction =		= Introduction =
	Globalyzer CLI can be deployed on a Continuous Globalization system. It enables i18n scanning of a project based on a Globalyzer <code>project.gproj</code> saved filed most likely at the top level directory of the source code; the results are then pushed to the Dashboard.		[[Terms_and_Definitions\|Globalyzer CLI]] can be deployed on a [[Terms_and_Definitions\|Continuous Globalization]] system. It enables [[Terms_and_Definitions\|i18n]] [[Terms_and_Definitions\|scanning]] of a project based on a Globalyzer <code>project.gproj</code> saved filed most likely at the top level directory of the source code; the results are then pushed to the [[Terms_and_Definitions\|Dashboard]].

	= Target User=		= Target User=