Skip to content

Conversation

@ramsessanchez
Copy link
Contributor

Copy of #3451
Branched off from Main and PR directly into main to avoid rebase challenges plaguing current Dev branch

@ramsessanchez ramsessanchez requested a review from a team as a code owner December 10, 2025 22:05
@ramsessanchez ramsessanchez changed the title Sdk release and CI-build pipelines are seperated and restructured in … Separate CI-Build and Sdk-Release pipelines Dec 10, 2025
Copy link

Copilot AI commented Dec 10, 2025

@ramsessanchez I've opened a new pull request, #3463, to work on those changes. Once the pull request is ready, I'll request review from you.

Copy link
Contributor

@MIchaelMainer MIchaelMainer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ci-build is packing and signing. That will add a lot of time. Do we need that to validate?

"$(Build.SourcesDirectory)"
displayName: 'Build and push docker images'
allowPackageConflicts: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This task should not be in ci-build. I think this is duplicated. Actually, the Deploy_to_Internal_Feed stage needs to be removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question, do we still want to deploy any pre-release versions to Internal Feed?
Perhaps we can add a condition where the sdk-release pipeline only releases to nuget on Tag commits but releases to internal on commits into main?

@ramsessanchez ramsessanchez merged commit fa1577d into main Dec 11, 2025
3 of 5 checks passed
@ramsessanchez ramsessanchez deleted the ramsess/seperateCIAndReleaseInMain branch December 11, 2025 01:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants