Repository navigation
Onboard CI pipelines to Arcade - #11
Conversation
Add pinned Arcade tooling and a non-shipping infrastructure validation project. Use public and 1ES official Arcade job templates while preserving existing pipeline triggers and pools. Defer product signing and publishing. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
donnie-msft
left a comment
There was a problem hiding this comment.
It would be helpful if the PR description could tell me how much of this is from templates (VMR or MicroBuild or 1ESPT, etc) and how much is our own ode. I think it's possibly all templates?
| <optionSet id="Espresso" displayName="Espresso"/> | ||
| <optionSet id="Parsers" displayName="Parsers"> | ||
| <optionSet id="Parser 22" displayName="POMHTML Parser options" helpText="POMHTML Parser options for Localization Studio."> | ||
| <option id="SetCharsetInfo" displayName="Set or add Charset information when Generating" helpText="Add Charset information to the Generated file. This is in the format <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">. This is based on the Project Target Langauge. If the dir attribute value in the HTML tag i.e. <HTML dir="ltr"> is not localizable or is missing, its value will be set automatically on Generate if the reading order of the target language is different from the source language."> |
There was a problem hiding this comment.
Is this managed by .NET templates? I just happened to notice a typo, not sure if we address it here or in another repo.
| <option id="SetCharsetInfo" displayName="Set or add Charset information when Generating" helpText="Add Charset information to the Generated file. This is in the format <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">. This is based on the Project Target Langauge. If the dir attribute value in the HTML tag i.e. <HTML dir="ltr"> is not localizable or is missing, its value will be set automatically on Generate if the reading order of the target language is different from the source language."> | |
| <option id="SetCharsetInfo" displayName="Set or add Charset information when Generating" helpText="Add Charset information to the Generated file. This is in the format <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">. This is based on the Project Target Language. If the dir attribute value in the HTML tag i.e. <HTML dir="ltr"> is not localizable or is missing, its value will be set automatically on Generate if the reading order of the target language is different from the source language."> |
There was a problem hiding this comment.
Yeah, this is managed by the .NET Arcade templates and the typo was fixed in dotnet/arcade#17394. I don't know when these changes be released.
All the files under The official pipeline retains the existing 1ES Pipeline Template wrapper. |
Summary
Onboard the repository’s existing PR and official CI pipelines to Arcade, replacing the Hello World smoke checks with toolset restore and an infrastructure build.
10.0.401and Arcade SDK10.0.0-beta.26505.115; add public package feeds, SDK imports, version metadata, and a Windows build entry point.eng/commonand add a non-shippingMicrosoft.Build.NoTargetsproject to validate the build foundation before product projects exist.The SDK package’s source manifest maps Arcade to
f6209a1c…, matching the vendored tooling. This change does not enable product compilation/tests, signing, packing, or release publishing.Validation
10.0.0-beta.26505.115.