Skip to content

Separate ci and release build pipelines - #3451

Closed
Ramses Sanchez-Hernandez (ramsessanchez) wants to merge 3 commits into
devfrom
ramsess/addSeperateReleasePipeline
Closed

Separate ci and release build pipelines#3451
Ramses Sanchez-Hernandez (ramsessanchez) wants to merge 3 commits into
devfrom
ramsess/addSeperateReleasePipeline

Conversation

@ramsessanchez

@ramsessanchez Ramses Sanchez-Hernandez (ramsessanchez) commented Dec 3, 2025

Copy link
Copy Markdown
Contributor

Separating the CI build pipelines from the release pipeline.
CI will only run on pushes into Dev and pull requests into Dev & Main.
Release will only run on Tag commits as that is the only time we release to Nuget feed.

@@ -138,106 +134,3 @@ extends:
publishVstsFeed: ${{ parameters.InternalFeed }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We should have build and validation run in ci-build. What's the plan here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Not sure I quite understand the question here. We are maintaining this CI pipeline as is for the most part, but removing the unused stages where we publish to nuget or to registry. The build validation occurs during the templates at lines 83, 89, 95 and finally at 109.

Comment thread .azure-pipelines/sdk-release.yml Outdated
@ramsessanchez

Copy link
Copy Markdown
Contributor Author

Closing as superseded by #3462

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.

2 participants