Update yml to support new signing requirements#80073
Update yml to support new signing requirements#80073shyamnamboodiripad merged 4 commits intodotnet:mainfrom
Conversation
JoeRobich
left a comment
There was a problem hiding this comment.
Does this need to be backported to our servicing branches?
We'll definitely need to. I can trigger those |
|
/backport to release/dev17.14 |
|
/backport to release/dev17.12 |
|
Started backporting to release/dev17.14: https://github.com/dotnet/roslyn/actions/runs/17331720121 |
|
Started backporting to release/dev17.12: https://github.com/dotnet/roslyn/actions/runs/17331722693 |
|
/backport to release/dev18.0 |
|
Started backporting to release/dev18.0: https://github.com/dotnet/roslyn/actions/runs/17331730244 |
|
/backport to release/dev16.11-vs-deps |
|
Started backporting to release/dev16.11-vs-deps: https://github.com/dotnet/roslyn/actions/runs/17331774845 |
) Backport of #80073 to release/dev18.0 /cc @dibarbet @shyamnamboodiripad ## Customer Impact ## Regression - [ ] Yes - [ ] No [If yes, specify when the regression was introduced. Provide the PR or commit if known.] ## Testing [How was the fix verified? How was the issue missed previously? What tests were added?] ## Risk [High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]
…0089) Backport of #80073 to release/dev17.14 /cc @dibarbet @shyamnamboodiripad ## Customer Impact ## Regression - [ ] Yes - [ ] No [If yes, specify when the regression was introduced. Provide the PR or commit if known.] ## Testing [How was the fix verified? How was the issue missed previously? What tests were added?] ## Risk [High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]
|
@dibarbet backporting to "release/dev16.11-vs-deps" failed, the patch most likely resulted in conflicts: $ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch
Applying: Update yml to support new signing requirements
Using index info to reconstruct a base tree...
M azure-pipelines-official.yml
Falling back to patching base and 3-way merge...
Auto-merging azure-pipelines-official.yml
CONFLICT (content): Merge conflict in azure-pipelines-official.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Update yml to support new signing requirements
Error: The process '/usr/bin/git' failed with exit code 128Please backport manually! |
…0087) Backport of #80073 to release/dev17.12 /cc @dibarbet @shyamnamboodiripad ## Customer Impact ## Regression - [ ] Yes - [ ] No [If yes, specify when the regression was introduced. Provide the PR or commit if known.] ## Testing [How was the fix verified? How was the issue missed previously? What tests were added?] ## Risk [High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]
|
/backport to release/dev17.10 |
|
Started backporting to release/dev17.10: https://github.com/dotnet/roslyn/actions/runs/17837863084 |
No description provided.