Integrating Build resources with existing loop and Teamspaces
You can integrate the previously created Build resources, including teams, mappings, and agent pools to an existing Teamspace and loop after you upgrade from DevOps Loop 1.0.2 to 1.0.3.
Before you begin
You must have completed the following tasks:
- Ensured that you have the administrator privileges in DevOps Loop.
- Ensured that you have a valid bearer token.
- Ensured that you have a loop ID, teamspace ID, and loop name.
Procedure
-
Create a team in Build by using the following API call:
curl -kX PUT "${LOOPDOMAIN}/build/rest2/team/loop/${loopId}" \ -H "Authorization: Bearer ${BEARER_TOKEN}" \ -H "Content-Type: application/json" \ -d '{ "name": "${LoopName}", "description": "", "type": "Loop", "teamspaceId": "${teamspaceId}", "roleMappings": [ { "role": "Platform User", "user": "${UserEmailAddress}", "authenticationRealm": "Platform_build_OIDC" } ] }'Replace all variables with actual values:
- loopId: Navigate to . Select the team created during loop initialization and loop ID can be found at the end of the URL.
- teamspaceId: Navigate to . Select the team created during Teamspace creation and teamspace ID can be found at the end of the URL
- LoopName: Use the loop's name, without any prefix.
- BEARER_TOKEN: Use a valid bearer token.
You can assign additional members in the
roleMappingsarray. Supported roles includePlatform UserandPlatform Admin. -
Perform the following steps to map resources to the newly created team in
Build:
- Add the required users to the new team.
- Configure the agent and assign it to the appropriate agent pool.
- Click Retry for the failed Team spaces after upgrading from DevOps Loop 1.0.2 to DevOps Loop 1.0.3 to complete the Teamspace creation.
Results
The Build environment is now successfully integrated into the previously created loops and Teamspaces after upgrading from DevOps Loop 1.0.2 to DevOps Loop 1.0.3.
