[APIView CI] Allow Build Job Re-run Without Artifact Publish Error When Package Already Exists

[raych1]

Problem

When a pipeline run fails during API review validation, approvals may be required in API View before proceeding. After receiving approval, users would prefer to re-run only the build job instead of the entire pipeline, saving time by not repeating all test and analysis jobs. However, attempting to re-run the build job results in the following error:

pipeline run

##[error]Artifact packages already exists for build 6049747.

Impact

This prevents efficient recovery from validation failures and forces unnecessary pipeline executions, leading to wasted time and build resources.

Proposed Solution

Introduce a mechanism for the build job to optionally skip the artifact publishing step if the target artifact already exists. This will:

• Allow users to re-run build jobs after validation steps are approved, without encountering duplicate artifact errors
• Avoid rerunning unrelated test and analysis jobs
• Improve pipeline efficiency and resource usage

Split the step of create/validate apiview in a separate stage could be a potential solution.

[praveenkuttappan]

@raych1 Your suggestion is to move APIView step completely into a different stage from current Build stage. This will require some good effort to make this change across all languages and pipeline also has some other steps like validation and update of package status to package work item as a dependency of apiview step.

Is this happening frequently to make this kind of change? Some pipeline has the ability to publish the package using a different artifact name when retrying. Can you please make that change in the publish artifact step to handle the retry instead of moving APIView and related steps into a different stage?