On Boarding a Globalyzer Project - Revision history

Olibouban at 17:23, 20 March 2024

2024-03-20T17:23:51Z

← Older revision		Revision as of 17:23, 20 March 2024
Line 1:		Line 1:
			= OBSOLETE =

	=Before On Boarding a Globalyzer Project =		=Before On Boarding a Globalyzer Project =
	Lingoport has created a [[Pre_Flight_Check\|Pre-flight Check]] for Globalyzer. Before on boarding a Globalyzer project, please do the pre-flight check.		Lingoport has created a [[Pre_Flight_Check\|Pre-flight Check]] for Globalyzer. Before on boarding a Globalyzer project, please do the pre-flight check.

2020-06-13T23:18:04Z

Source Code Management

← Older revision		Revision as of 23:18, 13 June 2020
Line 41:		Line 41:
	[[File:source_code_management.jpg\|700px]]		[[File:source_code_management.jpg\|700px]]

	'''Source Code Management''' section: Set up the Repository, Credentials, and Branch		'''Source Code Management''' section: Set up the Repository, Credentials, and Branch. For example if the Git repository is Acme/myproject and the code to work with is in the 'development' branch, then set the Repository URL to '''<nowiki>https://github.com/Acme/myproject.git</nowiki>'''. It is often easy to copy this from GitHub. For the branch, make sure to define it as '''/development'''. If the '/' is left off, there will be problems.

	==== Build Triggers ====		==== Build Triggers ====

2019-12-13T18:48:19Z

Before On Boarding a Globalyzer Project

← Older revision		Revision as of 18:48, 13 December 2019
Line 1:		Line 1:
	=Before On Boarding a Globalyzer Project =		=Before On Boarding a Globalyzer Project =
			Lingoport has created a [[Pre_Flight_Check\|Pre-flight Check]] for Globalyzer. Before on boarding a Globalyzer project, please do the pre-flight check.

	To on-board a Globalyzer project, some basic information is needed:		To on-board a Globalyzer project, some basic information is needed:

2019-12-13T18:01:48Z

Verifying the Automation Job

← Older revision		Revision as of 18:01, 13 December 2019
Line 73:		Line 73:
	To check if it completed successfully, select the project and look at the '''Build History'''		To check if it completed successfully, select the project and look at the '''Build History'''

	[[File:BuildHistoryNational.~~jpg~~\|500px]]		[[File:BuildHistoryNational.png\|500px]]

	The indicator should look like a blue ball. If it is a red ball, select it to go to '''Console Output''' and look for errors.		The indicator should look like a blue ball. If it is a red ball, select it to go to '''Console Output''' and look for errors.

2019-12-13T17:57:56Z

← Older revision		Revision as of 17:57, 13 December 2019
Line 66:		Line 66:

	For more information, see [[Project Configuration Files]]		For more information, see [[Project Configuration Files]]

			= Verifying the Automation Job =

			The Jenkins job should complete successfully and populate the Lingoport Dashboard.

			To check if it completed successfully, select the project and look at the '''Build History'''

			[[File:BuildHistoryNational.jpg\|500px]]

			The indicator should look like a blue ball. If it is a red ball, select it to go to '''Console Output''' and look for errors.



			[[File:DashboardNational.png\|700px]]

			If the indicator is blue, then login to the Lingoport Dashboard and verify that the project is on the Dashboard. The Globalyzer Dashboard will show the number of issues found and the rule sets that were used to scan the code as well as how much code was scanned.

			If there are problems at this point, please contact '''support@lingoport.com''' for assistance.

2019-12-13T17:01:20Z

Build

← Older revision		Revision as of 17:01, 13 December 2019
Line 56:		Line 56:

	Globalyzer requires a Project Definition File. Is is recommended that this is put in the repository in a lingoport folder, although it can be anywhere as long as it can be found. Here is an example of a [[Globalyzer_CI/CD_(Continuous_Integration_and_Continuous_Delivery)#Project_Definition_Format \|Project Definition File]].		Globalyzer requires a Project Definition File. Is is recommended that this is put in the repository in a lingoport folder, although it can be anywhere as long as it can be found. Here is an example of a [[Globalyzer_CI/CD_(Continuous_Integration_and_Continuous_Delivery)#Project_Definition_Format \|Project Definition File]].

			For the full instructions to setup a project definition file, see our
			[https://www.globalyzer.com/gzserver/help/referenceLite/project-definition-file-overview.html help page].

	==== Post Build Actions ====		==== Post Build Actions ====

2019-12-13T17:00:18Z

Build

← Older revision		Revision as of 17:00, 13 December 2019
Line 55:		Line 55:
	[[File:BuildGlobalyzerJenkins.png\|700px]]		[[File:BuildGlobalyzerJenkins.png\|700px]]

	Globalyzer requires a Project Definition File. Is is recommended that this is put in the repository in a lingoport folder, although it can be anywhere as long as it can be found. Here is an example of a [[Globalyzer_CI/CD_(Continuous_Integration_and_Continuous_Delivery)#Project_Definition_Format \|Project Definition File]]		Globalyzer requires a Project Definition File. Is is recommended that this is put in the repository in a lingoport folder, although it can be anywhere as long as it can be found. Here is an example of a [[Globalyzer_CI/CD_(Continuous_Integration_and_Continuous_Delivery)#Project_Definition_Format \|Project Definition File]].

	==== Post Build Actions ====		==== Post Build Actions ====

2019-12-13T16:59:56Z

Build

← Older revision		Revision as of 16:59, 13 December 2019
Line 55:		Line 55:
	[[File:BuildGlobalyzerJenkins.png\|700px]]		[[File:BuildGlobalyzerJenkins.png\|700px]]

	Globalyzer requires a Project Definition File. Is is recommended that this is put in the repository in a lingoport folder, although it can be anywhere as long as it can be found. Here is an example of a [Globalyzer_CI/CD_(Continuous_Integration_and_Continuous_Delivery)#Project_Definition_Format \|Project Definition File]		Globalyzer requires a Project Definition File. Is is recommended that this is put in the repository in a lingoport folder, although it can be anywhere as long as it can be found. Here is an example of a [[Globalyzer_CI/CD_(Continuous_Integration_and_Continuous_Delivery)#Project_Definition_Format \|Project Definition File]]

	==== Post Build Actions ====		==== Post Build Actions ====

2019-12-13T16:59:35Z

Build

← Older revision		Revision as of 16:59, 13 December 2019
Line 55:		Line 55:
	[[File:BuildGlobalyzerJenkins.png\|700px]]		[[File:BuildGlobalyzerJenkins.png\|700px]]

	Globalyzer requires a Project Definition File. Is is recommended that this is put in the repository in a lingoport folder, although it can be anywhere as long as it can be found.		Globalyzer requires a Project Definition File. Is is recommended that this is put in the repository in a lingoport folder, although it can be anywhere as long as it can be found. Here is an example of a [Globalyzer_CI/CD_(Continuous_Integration_and_Continuous_Delivery)#Project_Definition_Format \|Project Definition File]

	==== Post Build Actions ====		==== Post Build Actions ====

2019-12-13T16:53:32Z

General

← Older revision		Revision as of 16:53, 13 December 2019
Line 31:		Line 31:
	[[File:GeneralTab.png\|700px]]		[[File:GeneralTab.png\|700px]]

	*'''General''' section: Select the GitHub project and fill in the Project url		*'''General''' section: Select the GitHub project and fill in the Project url (if using git repositories)
	*'''Throttle Concurrent Builds''' should be checked.		*'''Throttle Concurrent Builds''' should be checked.
	*'''Throttle this project as part of one or more categories '''		*'''Throttle this project as part of one or more categories '''