Skip to content

Build Retention should be revisited  #2413

@epananth

Description

@epananth

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 ErrorActionPreference in 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:96cdb5beef6840178d85bc2c22028226@thread.skype/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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions