Skip to content
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

Re-created a GitHub build & test pipeline #183

Merged
merged 1 commit into from
Aug 29, 2024

Conversation

jstedfast
Copy link
Member

@jstedfast jstedfast commented Aug 28, 2024

Description of Change

Re-created a GitHub build & test pipeline

  • Updated UnitTests.csproj to use the latest MSTest.Adaptor/Framework nugets
  • Use dotnet test to run the unit tests

@jstedfast jstedfast force-pushed the dev/jestedfa/readd-github-action branch from d8ce77c to fb4e4ab Compare August 28, 2024 18:33
* Updated UnitTests.csproj to use the latest MSTest.Adaptor/Framework nugets
* Use `dotnet test` to run the unit tests
@jstedfast jstedfast force-pushed the dev/jestedfa/readd-github-action branch from fb4e4ab to 3171dfe Compare August 29, 2024 14:16
@jstedfast jstedfast requested a review from mgoertz-msft August 29, 2024 14:17
@jstedfast jstedfast changed the title Readd GitHub build pipeline Re-created a GitHub build & test pipeline Aug 29, 2024
if: success()
run: msbuild src\Microsoft.Xaml.Behaviors\Microsoft.Xaml.Behaviors.csproj /p:Configuration=Release -t:pack

- name: Upload NuGet Artifacts
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 the Upload step now that we have this in the Azure Pipeline?

Copy link
Member Author

Choose a reason for hiding this comment

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

I was wondering about that too

Copy link
Member

Choose a reason for hiding this comment

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

Never mind. This isn't uploading anything to nuget.org but just keeps these build artifacts for GH workflow runs, so we should keep it.

Copy link
Member

Choose a reason for hiding this comment

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

From GitHub Copilot :-)

GitHub stores artifacts in the "Actions" tab of your repository. Here's how you can view them:

Navigate to the Repository: Go to the repository where the workflow runs.

Access the Actions Tab: Click on the "Actions" tab at the top of the repository page.

Select a Workflow Run: Find and click on the workflow run that generated the artifacts. You can identify it by the workflow name and the date it ran.

View Artifacts: Once you're on the workflow run page, scroll down to the "Artifacts" section. Here you will see a list of artifacts that were uploaded during the workflow run. You can download them from this section.

You can also access them directly from the workflow run summary page.

@jstedfast jstedfast merged commit 1a72a76 into main Aug 29, 2024
2 checks passed
@jstedfast jstedfast deleted the dev/jestedfa/readd-github-action branch August 29, 2024 15:15
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