-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Testing new macos lane #3953
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
Testing new macos lane #3953
Conversation
34d6ea2
to
04612e0
Compare
04612e0
to
46c775a
Compare
b91aabd
to
9d8f659
Compare
Under the scenario where both a mono sample and non-mono sample are modified in the same pull request, is there a way to run the original build validation without the mono sample changes?
achieves this. |
I think you'll need to tweak the Get-MSBuildResults.ps1 script to exclude certain paths. |
1f8737e
to
c97b717
Compare
c97b717
to
58ae03a
Compare
7a44a71
to
e72c8fc
Compare
e72c8fc
to
7ab52c6
Compare
Summary
With the import of
dotnet/runtime
samples that demonstrate how to build iOS, Android, and wasm apps on top of the mono runtime, a check to ensure that these have built properly is needed. The mono samples need to pull down a runtime pack to properly build the application, sodotnet publish
will be used instead ofdotnet build
.The applications will not be ran for these checks. Ensuring that the applications can be built is the primary goal.
This PR looks to add another GitHub Actions workflow that targets these mono-samples.
When a file that influences the publish process is changed, the original build shall not be ran for the project, instead, the new one will be ran.
As seen in this PR, the original build check does not run for this PR, only
Publish Mono Samples
is ran.