Skip to content

Conversation

@Youssef1313
Copy link
Member

No description provided.


- name: Download packages from test-tools feed
run: |
dotnet run .github/workflows/PackageDownloader.cs -- ${{ github.event.inputs.mstest_version }} ${{ github.event.inputs.mstest_engine_version }} ${{ github.event.inputs.mtp_version }}
Copy link
Member Author

Choose a reason for hiding this comment

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

The basic idea here is:

  1. Packages are built via our internal pipeline, as usual.
  2. Packages are published to test-tools feed from our internal pipeline, as usual.
  3. This step will then download the packages from test-tools.
  4. The next step will authenticate to nuget. We will set Trusted Publishing for it to work. Unfortunately, trusted publishing isn't yet supported with AzDO Pipelines AFAIK, that's why I'm doing this with GitHub Actions.
  5. We push to nuget with the short-living key obtained in the previous step.

This simplifies our current approach to release to nuget.org which is very manual.

@blowdart Does that sound good? Any concerns?

Choose a reason for hiding this comment

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

It'd work. Do I think it's a good idea? No. Just publish from AzDO like everyone else, because now you not only have to carefully validate actions and azdo flows, which you're used to, but a whole new thing, a single .cs file

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