Skip to content

ci: set deployment to occur either manually or tagged commit - #2992

Merged
Michael Mainer (MIchaelMainer) merged 2 commits into
mainfrom
mmainer/updateci
Sep 10, 2025
Merged

Michael Mainer (MIchaelMainer) merged 2 commits into
mainfrom
mmainer/updateci

Conversation

@MIchaelMainer

@MIchaelMainer Michael Mainer (MIchaelMainer) commented Sep 10, 2025 •

Copy link
Copy Markdown
Contributor

Current settings only will deploy on runs from main.

Microsoft Reviewers: Open in CodeFlow

Copilot AI review requested due to automatic review settings September 10, 2025 22:08

Copilot AI left a comment

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.

Pull Request Overview

This PR modifies the Azure DevOps pipeline deployment conditions to allow deployments on tagged commits or manual triggers, expanding from the previous restriction to only deploy from the main branch.

Key changes:

  • Updates deployment condition to trigger on tagged commits or manual pipeline runs
  • Removes the requirement for deployments to only occur from the main branch

Comment thread .azure-pipelines/ci-build.yml Resolved
@gavinbarron

Copy link
Copy Markdown
Member

Michael Mainer (@MIchaelMainer) what use-case do we have for releasing the SDK from any other branch?

@MIchaelMainer

Copy link
Copy Markdown
Contributor Author

Gavin Barron (@gavinbarron) None. But we want to build from a tagged commit which should be in main branch. build.sourceBranch will be refs/tags/{version}. This pipeline will only automatically run from main.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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.

4 participants