ci: add dedicated nightly pipeline for C# emitter against TypeSpec Next#10755
Open
JoshLove-msft wants to merge 1 commit into
Open
ci: add dedicated nightly pipeline for C# emitter against TypeSpec Next#10755JoshLove-msft wants to merge 1 commit into
JoshLove-msft wants to merge 1 commit into
Conversation
Adds packages/http-client-csharp/eng/pipeline/nightly.yml so the nightly TypeSpec Next validation runs on its own ADO pipeline definition. This separates reporting from the publish pipeline and skips package publishing and the azure-sdk-for-net PR stage. The publish pipeline retains its UseTypeSpecNext parameter for manual runs as requested. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
JoshLove-msft
requested review from
ShivangiReja,
jorgerangel-msft,
joseharriaga,
jsquire and
m-nash
as code owners
microsoft-github-policy-service
Bot
added
the
emitter:client:csharp
commit: |
Contributor
|
No changes needing a change description found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
packages/http-client-csharp/eng/pipeline/nightly.ymlso the nightly TypeSpec Next validation for the C# emitter runs on its own ADO pipeline definition.Why
Today the nightly TypeSpec Next validation piggybacks on
publish.yml(scheduled runs flipUseTypeSpecNexton). That has two downsides:What
packages/http-client-csharp/eng/pipeline/nightly.ymltrigger: none/pr: none— schedule will be configured on the ADO pipeline definition (matching repo convention; no other emitter pipelines define schedules in YAML).UseTypeSpecNextparameter defaults totrue.Publish: ""none""passed toemitter-stages.yml→ Publish stage and theCreateAzureSdkForNetPRstage are not included.-UnitTests) plus theRegenCheckmatrix (toggleable viaRunRegenChecksparameter) so generation diffs against @next are surfaced in a separateCSharp_Regen_Teststage.publish.yml.publish.ymlis intentionally left untouched. ItsUseTypeSpecNextparameter andBuild.Reason == 'Schedule'override still work, so the existing capability is preserved. Once this pipeline is wired up in ADO, the schedule trigger can be moved off the publish definition.Follow-up (outside this PR)
packages/http-client-csharp/eng/pipeline/nightly.ymland set the nightly schedule there.