...

A second common solution is to store the buildSessionID of every component in a central place (database, folder component-specific,…) and create the Integration Build from these IDs.

For example, you can use a dedicated Variable Group in AzureDevOps Library section like in the image below:

...

Using Sealights' Public API

Resolving dynamically the components' details

...

A third common solution is to use Sealights Public APIs to programmatically retrieve the BSID of every component using specific criteria (the last build, a specific build from a certain date, build matching a certain naming convention…).

...

• /sl-api/v1/slim-builds (Get Builds API)

• or /sl-api/v1/slim-builds/resolve (Resolve Builds API).

Capturing the list of all active agents from a specific environment

Another solution is to take a snapshot of your environment by capturing all the agents up and running from that specific environment at the creation of your Integration Build.
This last solution relies on several technical assumptions and is a good starting point but not recommended as a persistent solution.

More details are shared in our dedicated documentation page: https://sealights.atlassian.net/wiki/spaces/SUP/pages/1898348552/Creating+a+JSON+file+listing+the+Integration+Build+s+Components#Using-the-list-of-agents-currently-active-in-a-specific-environment