Concept & Values
Sealights identifies OOB the modified/added code and reflects this in the Dashboard on a specific build - compared to its “Reference Build”.
The Reference Build can be, for example, the last build pushed to Production, or the last one promoted to the next branch (e.g. from feature-branch to develop then to main), or the last build from the previous sprint or first build from the current sprint…
By default, the reference build is the previous one and is defined per Branch.
Sealights highlights the untested modified/added code (for any app) based on date range and aggregates several builds analytics in the TGA report.
Both information can be accessed in the Dashboard, downloaded as raw data in a CSV file, or retrieved via Public API.
The Quality Gates can also be based on the Modified/added code level.
See: https://<customer_domain>.sealights.co/settings/quality-gates (replace the customer_domain with your account’s name)
This metric being retrievable via the Public API, you can define your custom Gates in your CI as well.
See: https://<customer_domain>.sealights.co/doc/public-api (replace the customer_domain with your account’s name)
How to set up manually
By default, the reference build is the previous one and is defined per Branch.
You can identify the current reference build from the reference build column for each application.
When there is a need to change the current reference build, click on the build history of the specific application (by hovering on its build column)
In the build history select the specific build
By hovering on top of the Quality gate column of the specific application click on the “Set reference build” button and approve you want to set it to the previous steps selected build.
This setting will take effect only from the next build.
How to set up via Sealights Public API
In the Sealights platform open “SeaLights API Reference” from the Help menu.
Search for “Set Reference Build” under Builds section. (See
/sl-api/v1/builds/{bsid}/reference)