Build Retention should be revisited
The staging pipeline failed to retain a build of a product repo in the Enable permanent build retention step and to unblock the pipeline we set continueOnError to true after determining that the issue is not blocking
We should revisit this fix and consider
- distinguishing between a build found exception as opposed to api error
- changing the
ErrorActionPreferencein the script - figuring out how to determine if a failure in this stage is blocking - does it depend on the specific build that's missing? and documenting it for the release team
Teams thread: https://teams.microsoft.com/l/message/19:[email protected]/1684152497666?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=147df318-61de-4f04-8f7b-ecd328c256bb&parentMessageId=1684152497666&teamName=.NET%20Eng%20Services&channelName=V-Team%20-%20Release%20Infrastructure&createdTime=1684152497666
- retention of the Release pipeline.
The points from the description are covered in https://github.com/dotnet/arcade-services/issues/2680. What is left is to discuss retaining the release pipeline runs