...
select the environment we want to build the composite in, the environments that had the Build Environment checkbox will appear in the dropdown
select the SCM Branch that was configured on the project, this will be pre-populated if there is only one configured Branch.
submit the request, this will initiate the Build workflow
...
Upon submission, the build workflow is initiated and the workflow steps are executed on the AZURE instance in the AZUREDEV environment(based on configurations provided). Upon completion of the workflow, the execution status will be successful.
...
With the successful execution of the build, a .zip file artifact is created(specific to Function App use case), stored in the artifact repository, and marked with the Project Version. Every build will generate a new Project Version. The generated artifact can be viewed from the Execution Id link and the Artifacts tab.
...
Now the composite can be deployed to an environment by selecting the icon as shown in the below screenshot.
...
The Project Version will be updated the same as the build project version. However, the dropdown will contain all previously create Project Versions
select the Environment that the deployment will be executed in
The Deploy Instance will be updated the same as the deploy instance on the General Configuration.
Additional input arguments(optional) can also be provided in case needed.
submit the request, this will initiate the Deploy workflow
...
Upon submission, the deploy workflow is initiated and the workflow steps are executed on the AZURE instance in the AZUREDEV environment(based on configurations provided), utilizing the endpoint. Upon completion of the workflow, the execution status will be successful. With the successful execution of the deployment, the Function will be deployed to the designated Azure Function App.
...