CLI Standardization Examples (Before vs After)

This section demonstrates how legacy, technology-specific CLI parameters map to the new standardized naming convention.

Java

After (Standardized)

java -jar sl-build-scanner.jar config \
  --token <token> \
  --appName my-app \
  --branchName release/1.0 \
  --buildName build-123 \
  --includePackages com.myapp.* \
  --excludePackages com.myapp.test.*

java -jar sl-build-scanner.jar scan \
  --token <token> \
  --buildSessionIdFile buildSessionId.txt \
  --scanDir ./target

Before (Legacy)

.NET

After (Standardized)

dotnet ./<agent-path>/SL.DotNet.dll scan \
  --token <token> \
  --buildSessionIdFile buildSessionId.txt \
  --scanDir ./bin

Before (Legacy)

Node.js

After (Standardized)

npx slnodejs config \
  --token <token> \
  --appName my-app \
  --branchName release/1.0 \
  --buildName build-123 \
  --failBuild true
  
npx slnodejs scan \
  --token <token> \ 
  --buildSessionId <id> \
  --scanDir <workspacepath> \
  --scmType {git|none} \
  --instrumentForBrowsers \
  --labId <labid> \
  --excludeSourceMapFiles {none|skipCopy|skipAndDelete} \
  --es6Modules

Before (Legacy)

Python

After (Standardized)

sl-python config \
  --token <token> \
  --appName <app-name> \
  --branchName <branch> \
  --buildName <build> \
  --scanDir <path> \
  --includeFiles <include> \
  --excludeFiles <exclude>

Before (Legacy)

Go

After (Standardized)

slgoagent config \
  --token <token> \
  --appName my-app \
  --branchName release/1.0 \
  --buildName build-123 \
  --labId <labid>

Before (Legacy)