Skip to content

Add dotnet host release pipeline #3061

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

jviau
Copy link
Contributor

@jviau jviau commented May 20, 2025

Issue describing the changes in this PR

resolves #issue_for_this_pr

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • I have added all required tests (Unit tests, E2E tests)

Additional information

Adds a pipeline to publish dotnet worker host nuget packages.

value: $(Pipeline.Workspace)/build/${{ parameters.artifactName }}
readonly: true
- name: staging_feed
value: public/infra-pre-release
Copy link
Contributor Author

@jviau jviau May 20, 2025

Choose a reason for hiding this comment

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

These names are not final; I have not created the feeds yet. Want to discuss them here or over teams.

The idea is to have 2 feed 'trains' to differentiate between packages that do and do not go to public nuget.org. These new feeds will be for the packages which do not go to nuget.org. What do we want to name them?

@jviau jviau requested a review from kshyju May 22, 2025 21:26
@@ -0,0 +1,152 @@
parameters:
- name: publishToProduction
Copy link
Member

Choose a reason for hiding this comment

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

Should we remove this? We only publish this to internal feed.

Copy link
Contributor Author

@jviau jviau May 28, 2025

Choose a reason for hiding this comment

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

"production" here is the feed the function host (and other repos) consume.

Unless you think this package has no need for a staging + "production" release?

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