Globalyzer CI/CD (Continuous Integration and Continuous Delivery) - Revision history

Olibouban: /* Language Support */

2025-02-12T21:50:04Z

Language Support

← Older revision		Revision as of 21:50, 12 February 2025
Line 238:		Line 238:
	* Perl,		* Perl,
	* PHP,		* PHP,
	* Qt,		* QT C++,
	* SQL (Oracle, MS SQL, MySQL, PostgreSQL),		* SQL (Oracle, MS SQL, MySQL, PostgreSQL),
	* Visual Basic (Classic, .NET),		* Visual Basic (Classic, .NET),

MaryH: /* Project Definition Format */

2019-06-18T21:57:37Z

Project Definition Format

← Older revision		Revision as of 21:57, 18 June 2019
Line 70:		Line 70:
	<report-path></report-path> <!-- may be specified via command line -->		<report-path></report-path> <!-- may be specified via command line -->
	<report-type></report-type> <!-- See 'Report Information' -->		<report-type></report-type> <!-- See 'Report Information' -->
			<report-priorities></report-priorities> <!-- optional. List of priorities to include in reports -->

	<data-dictionary-location></data-dictionary-location> <!-- optional -->		<data-dictionary-location></data-dictionary-location> <!-- optional -->

Rdaly: /* Using Globalyzer Lite in a General CI/CD integration */

2019-06-14T20:37:30Z

Using Globalyzer Lite in a General CI/CD integration

← Older revision		Revision as of 20:37, 14 June 2019
Line 22:		Line 22:
	== Using Globalyzer Lite in a General CI/CD integration ==		== Using Globalyzer Lite in a General CI/CD integration ==

	To get started using Globalyzer Lite in your CI/CD integration, please refer to [Globalyzer_Lite_CICD_Integration \|Globalyzer Lite CI/CD integration]		To get started using Globalyzer Lite in your CI/CD integration, please refer to [[Globalyzer_Lite_CICD_Integration \|Globalyzer Lite CI/CD integration]]

	== Using Globalyzer Lite from a command line ==		== Using Globalyzer Lite from a command line ==

Rdaly: /* Using Globalyzer Lite in a General CI/CD integration */

2019-06-14T20:37:10Z

Using Globalyzer Lite in a General CI/CD integration

← Older revision		Revision as of 20:37, 14 June 2019
Line 22:		Line 22:
	== Using Globalyzer Lite in a General CI/CD integration ==		== Using Globalyzer Lite in a General CI/CD integration ==

	To get started using Globalyzer Lite in your CI/CD integration, please refer to [[Globalyzer_Lite_CICD_Integration Globalyzer Lite CI/CD integration]]		To get started using Globalyzer Lite in your CI/CD integration, please refer to [Globalyzer_Lite_CICD_Integration \|Globalyzer Lite CI/CD integration]

	== Using Globalyzer Lite from a command line ==		== Using Globalyzer Lite from a command line ==

Rdaly: /* Using Globalyzer Lite in a General CI/CD integration */

2019-06-14T20:35:13Z

Using Globalyzer Lite in a General CI/CD integration

← Older revision		Revision as of 20:35, 14 June 2019
Line 22:		Line 22:
	== Using Globalyzer Lite in a General CI/CD integration ==		== Using Globalyzer Lite in a General CI/CD integration ==

	To get started using Globalyzer Lite in your CI/CD integration, please refer to [Globalyzer_Lite_CICD_Integration Globalyzer Lite CI/CD integration]		To get started using Globalyzer Lite in your CI/CD integration, please refer to [[Globalyzer_Lite_CICD_Integration Globalyzer Lite CI/CD integration]]

	== Using Globalyzer Lite from a command line ==		== Using Globalyzer Lite from a command line ==

Rdaly at 20:34, 14 June 2019

2019-06-14T20:34:46Z

← Older revision		Revision as of 20:34, 14 June 2019
Line 4:		Line 4:
	[[File:GlobalyzerDashboard.png \|700px]]		[[File:GlobalyzerDashboard.png \|700px]]

	== Using Globalyzer Lite in a Continuous Globalization System ==		== Using Globalyzer Lite in Lingoport's Continuous Globalization System ==

	If the Lingoport Continuous Globalization System was installed and configured using the Stack Installer or Stack Updater, then Globalyzer Lite has already been integrated into the system.		If the Lingoport Continuous Globalization System was installed and configured using the Stack Installer or Stack Updater, then Globalyzer Lite has already been integrated into the system.
Line 19:		Line 19:

	You may also pass the reports to your own reporting system.		You may also pass the reports to your own reporting system.

			== Using Globalyzer Lite in a General CI/CD integration ==

			To get started using Globalyzer Lite in your CI/CD integration, please refer to [Globalyzer_Lite_CICD_Integration Globalyzer Lite CI/CD integration]

	== Using Globalyzer Lite from a command line ==		== Using Globalyzer Lite from a command line ==

Rdaly: /* Exit Error Codes */

2019-06-13T16:20:52Z

Exit Error Codes

← Older revision		Revision as of 16:20, 13 June 2019
Line 210:		Line 210:
	\| PROJECT_PATH_DOES_NOT_EXIST \|\| style="padding-left: 15px;" \| 53		\| PROJECT_PATH_DOES_NOT_EXIST \|\| style="padding-left: 15px;" \| 53
	\|-		\|-
			\| ATTEMPT_TO_READ_RC_FILE_FAILED \|\| style="padding-left: 15px;" \| 55
	\| \|\|		\| \|\|

Rdaly: /* Exit Error Codes */

2019-06-13T16:19:47Z

Exit Error Codes

← Older revision		Revision as of 16:19, 13 June 2019
Line 195:		Line 195:
	\|-		\|-
	\| GLOBALYZER_API_EXCEPTION \|\| style="padding-left: 15px;" \| 31		\| GLOBALYZER_API_EXCEPTION \|\| style="padding-left: 15px;" \| 31
			\|-
			\| GLOBALYZER_CLIENT_SERVER_MISMATCH \|\| style="padding-left: 15px;" \| 32
	\|- style="height:20px"		\|- style="height:20px"
	\|-		\|-

Rdaly: /* Exit Error Codes */

2019-06-13T16:18:39Z

Exit Error Codes

← Older revision		Revision as of 16:18, 13 June 2019
Line 169:		Line 169:
	\|-		\|-
	\| EXIT_NORMAL \|\| style="padding-left: 15px;" \| 0		\| EXIT_NORMAL \|\| style="padding-left: 15px;" \| 0
			\|-
			\| NULL_POINTER_EXCEPTION \|\| style="padding-left: 15px;" \| 1
	\|-		\|-
	\| \|\|		\| \|\|

Rdaly: /* Using Local Rulesets */

2019-06-13T15:54:10Z

Using Local Rulesets

← Older revision		Revision as of 15:54, 13 June 2019
Line 238:		Line 238:
	Rule sets are stored in local zip files rather than retrieved from the Server.		Rule sets are stored in local zip files rather than retrieved from the Server.

	These rule set files can either be exported directly from the Server and copied to your <code>project-path/lingoport</code> directory, or exported from the ~~Client~~ as an option when exporting your Globalyzer Workbench project to a Globalyzer Lite Project Definition File (Select <b>File->Export->Globalyzer->Export Project Definition (Lite)</b>).		===Creating the local ruleset files===
			These rule set files can either be exported directly from the Server and copied to your '''<code>project-path/lingoport</code>''' directory, or exported from the Globalyzer Workbench client as an option when exporting your Globalyzer Workbench project to a Globalyzer Lite Project Definition File (Select <b>File->Export->Globalyzer->Export Project Definition (Lite)</b>).

	<br>		<br>
Line 246:		Line 247:
	<br>		<br>

			===Using Local Rule Sets===
	To use Local Rule Sets, set the <b>use-local-rulesets</b> attribute to true in the Lite [[Globalyzer Lite#Project_Definition_Format\|Project Definition file]].		To use Local Rule Sets, set the <b>use-local-rulesets</b> attribute to true in the Lite [[Globalyzer Lite#Project_Definition_Format\|Project Definition file]].

	When using local rule sets, you do not need to specify username/password/server information in your Project Definition File.		When using local rule sets, you do not need to specify username/password/server information in your Project Definition File, but if you have a '''<home>/.globalyzerrc''' file the server information still must match the Project Definition File.

	<br>		<br>
Line 257:		Line 259:


	When using local rule sets, Globalyzer will try to access the rule set on the server ~~if a local rule set is not found~~ and the login information is available,		When using local rule sets, if a local rule set is not found, Globalyzer will try to access the rule set on the server and the login information is available,

	Use of this feature requires a '''Globalyzer License''' to be downloaded from the Server (from the Client Download page) and stored on your local machine.		Use of this feature requires a '''Globalyzer License''' to be downloaded from the Server (from the Client Download page) and stored on your local machine.
Line 269:		Line 271:

	Place this license file in the following default locations, per OS:		Place this license file in the following default locations, per OS:
	* Windows - C:\Lingoport		* Windows - <code>C:\Lingoport</code>
	* Linux - {userhome}/lingoport		* Linux - <code>{userhome}/lingoport</code> (<code>/var/lib/jenkins/lingoport</code> for the jenkins user on the Lingoport G11n system)
	* Mac - /Applications/Lingoport		* Mac - <code>/Applications/Lingoport</code>

	=== Best Practice ===		=== Best Practice ===
	* From the Workbench, export the the Lite ~~project definition file~~ and Local Rule Sets in the '''lingoport''' directory under the '''top level directory of the repository'''.		* From the Globalyzer Workbench, export the the Lite Project Definition File and Local Rule Sets in the '''lingoport''' directory under the '''top level directory of the repository'''.
	* Commit/Push the lingoport directory with the local Rule Set(s) and the ~~project definition file~~ to your repository		* Commit/Push the lingoport directory with the local Rule Set(s) and the Project Definition File to your repository

	By following this practice, you ensure that the Rule Sets are maintained together with the source code; When either a '''CICD''' system or a developer with an '''IDE with Lite''' use the Locale Rule Sets to scan the code, the location of the files is standard and no specific customization is needed.		By following this practice, you ensure that the Rule Sets are maintained together with the source code; When either a '''CICD''' system or a developer with an '''IDE with Lite''' use the Locale Rule Sets to scan the code, the location of the files is standard and no specific customization is needed.