Globalyzer Dashboard FAQ - Revision history

Olibouban: /* Limit files uploaded to the Dashboard to be files scanned by Globalyzer */

2018-12-04T23:55:17Z

Limit files uploaded to the Dashboard to be files scanned by Globalyzer

← Older revision		Revision as of 23:55, 4 December 2018
Line 35:		Line 35:


	= Limit files uploaded to the Dashboard to be files scanned by Globalyzer =		= Limit files uploaded to the Dashboard to be files scanned by Globalyzer and associated Resource Files =

	A project is made up of one or more scans, and each scan processes source files with configured file extensions.		A project is made up of one or more scans, and each scan processes source files with configured file extensions.

Olibouban: /* Limit files uploaded to the Dashboard to be files scanned by Globalyzer */

2018-12-04T23:54:14Z

Limit files uploaded to the Dashboard to be files scanned by Globalyzer

← Older revision		Revision as of 23:54, 4 December 2018
Line 49:		Line 49:

	For a project containing a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:		For a project containing a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:
	sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.~~jspf~~,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml,*/.json,*/.properties		sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.spf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml,*/.json,*/.properties
	if the resource files are .json and .properties files.		if the resource files are .json and .properties files.

Olibouban: /* Limit files uploaded to the Dashboard to be files scanned by Globalyzer */

2018-12-04T23:53:51Z

Limit files uploaded to the Dashboard to be files scanned by Globalyzer

← Older revision		Revision as of 23:53, 4 December 2018
Line 45:		Line 45:
	You need to include all the extensions for all the scans in your project and the extensions for the resource files (.properties, .resx, etc.).		You need to include all the extensions for all the scans in your project and the extensions for the resource files (.properties, .resx, etc.).
	For example, for a project containing only a Java scan, you would add the following line to your sonar-project.properties file:		For example, for a project containing only a Java scan, you would add the following line to your sonar-project.properties file:
	~~<code>~~sonar.inclusions=*/.java,*/.jsp,*/.jspf,*/.jspx,*/.properties~~</code>~~		sonar.inclusions=*/.java,*/.jsp,*/.jspf,*/.jspx,*/.properties
	if the resource files are .properties files.		if the resource files are .properties files.

	For a project containing a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:		For a project containing a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:
	~~<code>~~sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml,*/.json,*/.properties~~</code>~~		sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml,*/.json,*/.properties
	if the resource files are .json and .properties files.		if the resource files are .json and .properties files.

	Below is the list of rule set languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties file; that is, they should match.		Below is the list of rule set languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties file; that is, they should match.

Olibouban: /* Limit files uploaded to the Dashboard to be files scanned by Globalyzer */

2018-12-04T23:52:59Z

Limit files uploaded to the Dashboard to be files scanned by Globalyzer

← Older revision		Revision as of 23:52, 4 December 2018
Line 45:		Line 45:
	You need to include all the extensions for all the scans in your project and the extensions for the resource files (.properties, .resx, etc.).		You need to include all the extensions for all the scans in your project and the extensions for the resource files (.properties, .resx, etc.).
	For example, for a project containing only a Java scan, you would add the following line to your sonar-project.properties file:		For example, for a project containing only a Java scan, you would add the following line to your sonar-project.properties file:
	<code>sonar.inclusions=*/.java,*/.jsp,*/.jspf,*/.jspx,*/.properties</code>		<code>sonar.inclusions=*/.java,*/.jsp,*/.jspf,*/.jspx,*/.properties</code>
	if the resource files are .properties files.		if the resource files are .properties files.

	For a project containing a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:		For a project containing a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:
	<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml,*/.json,*/.properties</code>		<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml,*/.json,*/.properties</code>
	if the resource files are .json and .properties files.		if the resource files are .json and .properties files.

Olibouban: /* Limit files uploaded to the Dashboard to be files scanned by Globalyzer */

2018-12-04T23:52:39Z

Limit files uploaded to the Dashboard to be files scanned by Globalyzer

← Older revision		Revision as of 23:52, 4 December 2018
Line 46:		Line 46:
	For example, for a project containing only a Java scan, you would add the following line to your sonar-project.properties file:		For example, for a project containing only a Java scan, you would add the following line to your sonar-project.properties file:
	<code>sonar.inclusions=*/.java,*/.jsp,*/.jspf,*/.jspx,*/.properties</code>		<code>sonar.inclusions=*/.java,*/.jsp,*/.jspf,*/.jspx,*/.properties</code>
	if the resource files are .properties files.		if the resource files are .properties files.

	For a project containing a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:		For a project containing a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:
	<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml,*/.json,*/.properties</code>		<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml,*/.json,*/.properties</code>
	if the resource files are .json and .properties files.		if the resource files are .json and .properties files.

	Below is the list of rule set languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties file; that is, they should match.		Below is the list of rule set languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties file; that is, they should match.

Olibouban: /* Limit files uploaded to the Dashboard to be files scanned by Globalyzer */

2018-12-04T23:52:14Z

Limit files uploaded to the Dashboard to be files scanned by Globalyzer

← Older revision		Revision as of 23:52, 4 December 2018
Line 43:		Line 43:
	Note: For a project named Acme.Widget, the file would be typically located under ''~jenkins/Lingoport_Data/Dashboard/Projects/Acme.Widget/sonar-project.properties.''		Note: For a project named Acme.Widget, the file would be typically located under ''~jenkins/Lingoport_Data/Dashboard/Projects/Acme.Widget/sonar-project.properties.''

	You need to include all the extensions for all the scans in your project.		You need to include all the extensions for all the scans in your project and the extensions for the resource files (.properties, .resx, etc.).
	For example, ~~if your~~ project ~~contained~~ only a Java scan, you would add the following line to your sonar-project.properties file:		For example, for a project containing only a Java scan, you would add the following line to your sonar-project.properties file:
	<code>sonar.inclusions=*/.java,*/.jsp,*/.jspf,*/.jspx</code>		<code>sonar.inclusions=*/.java,*/.jsp,*/.jspf,*/.jspx,*/.properties</code>
			if the resource files are .properties files.

	~~If your~~ project ~~contained~~ a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:		For a project containing a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:
	<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml</code>		<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml,*/.json,*/.properties</code>
			if the resource files are .json and .properties files.

	Below is the list of rule set languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties file; that is, they should match.		Below is the list of rule set languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties file; that is, they should match.

Olibouban: /* Limit files uploaded to the Dashboard to be files scanned by Globalyzer */

2018-12-04T20:11:54Z

Limit files uploaded to the Dashboard to be files scanned by Globalyzer

← Older revision		Revision as of 20:11, 4 December 2018
Line 41:		Line 41:
	By default, all files found within your project's base path (the default setting of <b>sonar.sources</b>) are uploaded to the Dashboard, even ones that aren't scanned.		By default, all files found within your project's base path (the default setting of <b>sonar.sources</b>) are uploaded to the Dashboard, even ones that aren't scanned.
	To limit what is uploaded, you can configure the <b>sonar.inclusions</b> property in the <b>sonar-project.properties</b> file for your project.		To limit what is uploaded, you can configure the <b>sonar.inclusions</b> property in the <b>sonar-project.properties</b> file for your project.
			Note: For a project named Acme.Widget, the file would be typically located under ''~jenkins/Lingoport_Data/Dashboard/Projects/Acme.Widget/sonar-project.properties.''

	You need to include all the extensions for all the scans in your project.		You need to include all the extensions for all the scans in your project.

MaryH: /* Limit files uploaded to the Dashboard to be files scanned by Globalyzer */

2018-12-04T19:26:33Z

Limit files uploaded to the Dashboard to be files scanned by Globalyzer

← Older revision		Revision as of 19:26, 4 December 2018
Line 49:		Line 49:
	<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml</code>		<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml</code>

	Below is the list of rule set languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties; that is, they should match.		Below is the list of rule set languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties file; that is, they should match.

	{\| class="wikitable"		{\| class="wikitable"

MaryH: /* Limit files uploaded to the Dashboard to be files scanned by Globalyzer */

2018-12-04T19:26:08Z

Limit files uploaded to the Dashboard to be files scanned by Globalyzer

← Older revision		Revision as of 19:26, 4 December 2018
Line 49:		Line 49:
	<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml</code>		<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml</code>

	Below is the list of languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties; that is, they should match.		Below is the list of rule set languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties; that is, they should match.

	{\| class="wikitable"		{\| class="wikitable"

MaryH: /* Limit files uploaded to the Dashboard to be files scanned by Globalyzer */

2018-12-04T19:25:42Z

Limit files uploaded to the Dashboard to be files scanned by Globalyzer

← Older revision		Revision as of 19:25, 4 December 2018
Line 49:		Line 49:
	<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml</code>		<code>sonar.inclusions=*/.as,*/.asax,*/.ascx,*/.asp,*/.aspx,*/.cshtml,*/.ejs,*/.htm,*/.html,*/.java,*/.js,*/.jsp,*/.jspf,*/.jspx,*/.mas,*/.mi,*/.php,*/.xhtml</code>

	Below is the list of languages and ~~the~~ sonar.inclusions property ~~set to their default file extensions~~. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties; that is, they should match.		Below is the list of languages and their corresponding sonar.inclusions property. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties; that is, they should match.

	{\| class="wikitable"		{\| class="wikitable"