We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a general strategy we can make artifact publishing idempotent to job re-runs?
Example:
In publish-cli.yml (and anywhere else), when we have a pipeline artifact being published:
- task: 1ES.PublishPipelineArtifact@1 inputs: targetPath: release artifact: UploadedReleaseArtifacts
And in a subsequent step such as create-pull-request, fails due to a flaky issue. On a rerun, we will get an error:
##[error]Artifact UploadedReleaseArtifacts already exists for build 4153919.
Here's a recent build run demonstrating this issue.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there a general strategy we can make artifact publishing idempotent to job re-runs?
Example:
In publish-cli.yml (and anywhere else), when we have a pipeline artifact being published:
And in a subsequent step such as create-pull-request, fails due to a flaky issue. On a rerun, we will get an error:
Here's a recent build run demonstrating this issue.
The text was updated successfully, but these errors were encountered: