Standardized CLI Parameters Migration

Why This Matters

SeaLights CLI parameters are now standardized across all technologies to make configuration:

  • Consistent – same parameter = same meaning everywhere

  • Simple – easier to learn and remember

  • Scalable – seamless across multi-tech environments


What’s Changing

All CLI parameters now follow:

  • Prefix: --

  • Format: lower camel case

Examples

Before
After

-buildsessionid

--buildSessionId

-appname

--appName

-branch

--branchName

-build

--buildName

-workspacePath / -binDir

--scanDir

-loglevel

--logLevel

-failonerror

--failOnError


Good News: No Breaking Changes

  • Existing parameters still work (supported as aliases)

  • Migration can be gradual

  • No immediate action required


1

Identify

Find where SeaLights CLI is used:

  • CI/CD pipelines

  • Build scripts

  • Test runners

2

Replace

Update to standardized parameters:

3

Validate

After updates, confirm:

  • Builds complete successfully

  • Coverage is reported

  • Test stages are visible


Best Practice

  • Use only standardized parameters for all new implementations

  • Keep naming consistent across all technologies


When Are You Done?

You’re fully migrated when:

  • All pipelines use standardized parameters

  • No legacy naming remains

  • Same CLI structure across all tech stacks


Need Help?

If you’re unsure how to migrate your setup, reach out to your SeaLights representative.

Last updated

Was this helpful?