Skip to content
New issue

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

Allow for setting of isOfficialBuild when uploading intermediate artifacts #100528

Merged
merged 1 commit into from
Apr 2, 2024

Conversation

LoopedBard3
Copy link
Member

Allow for setting of isOfficialBuild when uploading intermediate artifacts.

After the update #99433, the performance pipeline runs started failing due to not being able to find 1ES.PublishBuildArtifacts, example run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2420076&view=results. This was due to the upload-intermediate-artifacts-step setting the job as an official build for the actual upload, where we use it as part of non-official builds. As such, I added the parameter isOfficialBuild with the default of true to allow for non-official build uses of the upload-intermediate-artifacts-step.yml.

Test run showing that this fixes the yaml parsing error: https://dev.azure.com/dnceng/internal/_build/results?buildId=2420143&view=results

@DrewScoggins
Copy link
Member

Is there a matching PR for the arcade repo? I assume that stuff in eng/common comes from there, and will get overwritten when we take an arcade update.

@LoopedBard3
Copy link
Member Author

I am assuming it will not get overwritten as PR that made the initial change was not an arcade update as far as I can tell, but if someone knows for sure, please weigh in.

@DrewScoggins
Copy link
Member

No, you are right. I didn't see it was eng/pipelines/common.

@LoopedBard3 LoopedBard3 merged commit 254012e into dotnet:main Apr 2, 2024
152 of 156 checks passed
@LoopedBard3 LoopedBard3 deleted the PerfFixYamlAfter1ESUpdate branch April 2, 2024 20:11
matouskozak pushed a commit to matouskozak/runtime that referenced this pull request Apr 30, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants