CodeScene - Revision history

Kenneth: /* Windows CLI Tools Installation */

2026-02-02T01:10:50Z

Windows CLI Tools Installation

← Older revision		Revision as of 01:10, 2 February 2026
Line 86:		Line 86:
	.\install-cs-tool.ps1		.\install-cs-tool.ps1

			May need to set Powershell permissions first (if you have never run Powershell scripts before):
			Set-ExecutionPolicy RemoteSigned

			Set access token:
	$env:CS_ACCESS_TOKEN = 'your-access-token'		$env:CS_ACCESS_TOKEN = 'your-access-token'

Kenneth: /* Untrusted On-Premise CodeScene Server - Custom SSL Certificate */

2026-02-02T00:48:37Z

Untrusted On-Premise CodeScene Server - Custom SSL Certificate

← Older revision		Revision as of 00:48, 2 February 2026
Line 155:		Line 155:
	=== Untrusted On-Premise CodeScene Server - Custom SSL Certificate ===		=== Untrusted On-Premise CodeScene Server - Custom SSL Certificate ===

	Okay, so you didn't pay for an official SSL Certificate? Sigh, Java is the worst when it comes to dealing with Custom SSL Certificates. Sorry. But you've made your bed, and wish to sleep in it, so buckle up, and here we go...		Okay, so you didn't pay for an official SSL Certificate ''(or you are stuck with a Corporate SSL Proxy Certificate)''? Sigh, Java is the worst when it comes to dealing with Custom SSL Certificates. Sorry. But you've made your bed, and wish to sleep in it, so buckle up, and here we go...

	Error:		Error:

Kenneth: /* = Use Firefox to Collect the SSL Certificate Chain */

2026-02-02T00:47:40Z

= Use Firefox to Collect the SSL Certificate Chain

← Older revision		Revision as of 00:47, 2 February 2026
Line 168:		Line 168:
	* you will need to build a custom Java Keystore, and every command, tool, and application will need to reference this custom Keystore, and the way you reference the Keystore with each application is different. It's ugly. Very ugly. Sorry.		* you will need to build a custom Java Keystore, and every command, tool, and application will need to reference this custom Keystore, and the way you reference the Keystore with each application is different. It's ugly. Very ugly. Sorry.

	==== Use Firefox to Collect the SSL Certificate Chain ===		==== Use Firefox to Collect the SSL Certificate Chain ====

	First, collect the SSL Certificate chain. This is from the perspective of the system trying to access the CodeScene server. (This SSL chain may change if the system tries to connect via a VPN proxy, which may use a Corporate SSL proxy, so you may need a second keystore)		First, collect the SSL Certificate chain. This is from the perspective of the system trying to access the CodeScene server. (This SSL chain may change if the system tries to connect via a VPN proxy, which may use a Corporate SSL proxy, so you may need a second keystore)

Kenneth: /* SSL Certificate Issues */

2026-02-02T00:47:30Z

SSL Certificate Issues

@@ Line 132: / Line 132: @@
 ==== Can't Wait on IT, Test Now ====
-If you don't want to wait for IT, you can test it out by checking out the next section, "Custom SSL Certificate"...
+If you don't want to wait for IT, you can test it out by checking out the section below, "Custom SSL Certificate"...
-But first, collect the SSL Certificate chain:
+Solution:
 Use Firefox, view the SSL certificate chain, and export it out.  (Click the lock in the address bar, select Connection Secure, select More Information, View Certificate, under Miscellaneious select Download "PEM (chain)".
@@ Line 160: / Line 196: @@
 etc...
 ==== Install OpenJDK for Keytool ====
@@ Line 200: / Line 222: @@
 ==== Test CS-CLI with Keystore ====
-To use the keystore you will need to inject it in various ways with Visual Code, CS-CLI, CS-MCP, etc.  For the CS-CLI, for example:
+To use the keystore you will need to inject it in various ways with Visual Code, CS-CLI, CS-MCP, etc.  But, for the CS-CLI specifically, for example:
   # Powershell example
@@ Line 207: / Line 229: @@
   cs review -D"javax.net.ssl.trustStore=C:/code/codescene.jks" -D"javax.net.ssl.trustStorePassword=changeit"
-Note: the java parameters use forward slashes "/" not back slashes "\" - I know this is windows, and this may break some brains.
+Note: the java parameters use forward slashes "/" not back slashes "\" - I know this is Windows, and this may break some brains.
 Note: once the license has been cached, you should be able to call the CS-CLI command again without the keystore parameters, at least until the cached license expires:
@@ Line 217: / Line 239: @@
   %APPDATA%\Codescene
-If you wish to force the license to be reaquired, delete this folder, and rerun the CS-CLI command
+If you wish to force the license to be reacquired, delete this folder, and rerun the CS-CLI command
 == keywords ==

Kenneth: /* Untrusted SSL Certificate - Corporate SSL Proxy */

2026-02-02T00:38:18Z

Untrusted SSL Certificate - Corporate SSL Proxy

← Older revision		Revision as of 00:38, 2 February 2026
Line 233:		Line 233:
	* First - cry. Java is the worst at dealing with custom SSL keystores. Sorry.		* First - cry. Java is the worst at dealing with custom SSL keystores. Sorry.
	* Second - See the steps under "Untrusted On-Premise CodeScene Server - Custom SSL Certificate". Use Firefox to export the SSL Chain, and collect the PEM file.		* Second - See the steps under "Untrusted On-Premise CodeScene Server - Custom SSL Certificate". Use Firefox to export the SSL Chain, and collect the PEM file.

			== keywords ==

Kenneth: /* Untrusted SSL Certificate - Corporate SSL Proxy */

2026-02-02T00:38:01Z

Untrusted SSL Certificate - Corporate SSL Proxy

← Older revision		Revision as of 00:38, 2 February 2026
Line 230:		Line 230:
	</pre>		</pre>

	Solution		Solution:

	* First - cry. Java is the worst at dealing with custom SSL keystores. Sorry.		* First - cry. Java is the worst at dealing with custom SSL keystores. Sorry.
			* Second - See the steps under "Untrusted On-Premise CodeScene Server - Custom SSL Certificate". Use Firefox to export the SSL Chain, and collect the PEM file.
	* Second - ~~okay~~, ~~so you still want to continue?~~

Kenneth: /* CLI - Check */

2026-02-02T00:36:18Z

CLI - Check

← Older revision		Revision as of 00:36, 2 February 2026
Line 11:		Line 11:
	Check a specific file for code health issues		Check a specific file for code health issues
	cs check [file]		cs check [file]
	cs ~~review~~ test.c
	cs ~~review~~ test.py		<pre>
			EXAMPLES
			$ cs check test.c Check the file test.c
			$ cs check master:./test.c Check the file test.c on the master branch
			$ cs check 801b0c0f:./test.c Check the file test.c at the given commit
			$ cs check --file-name test.c < test.c Read file data from stdin
			</pre>

	=== CLI - Review ===		=== CLI - Review ===

Kenneth: /* CLI - Review */

2026-02-02T00:36:06Z

CLI - Review

← Older revision		Revision as of 00:36, 2 February 2026
Line 18:		Line 18:
	Score a file, and provide a review		Score a file, and provide a review
	cs review [file]		cs review [file]
	cs review test.c
	cs review test.py		<pre>
			EXAMPLES
			$ cs review test.c Check the file test.c
			$ cs review test.c --output-format json Check test.c and output the results as json
			$ cs review master:./test.c Check the file test.c on the master branch
			$ cs review 801b0c0f:./test.c Check the file test.c at the given commit
			$ cs review --file-name test.c < test.c Read file data from stdin
			</pre>

	=== CLI - Update ===		=== CLI - Update ===

Kenneth: /* CLI Usage */

2026-02-02T00:35:40Z

CLI Usage

@@ Line 7: / Line 7: @@
   https://codescene.io/docs/cli/index.html
-=== CLI Usage ===
+=== CLI - Check ===
-  cs review
+Check a specific file for code health issues
 === CLI Configuration ===

Kenneth: /* Linux CLI Tools Installation */

2026-02-02T00:25:47Z

Linux CLI Tools Installation

← Older revision		Revision as of 00:25, 2 February 2026
Line 42:		Line 42:
	Run a code scene command:		Run a code scene command:
	cs review		cs review

			Installs the tool to:
			%LOCALAPPDATA%\Programs\CodeScene\cs.exe

	=== Linux CLI Tools Installation ===		=== Linux CLI Tools Installation ===
Line 54:		Line 57:
	If using an onpremise code scene server:		If using an onpremise code scene server:
	export CS_ONPREM_URL=https://codescene.example.com		export CS_ONPREM_URL=https://codescene.example.com

			Installs the tool to:
			~/.local/bin/cs
			$HOME/.local/bin/cs
			/home/USER/.local/bin/cs

	== Issues ==		== Issues ==