[ci] macos12 is no longer available, use macos14.
#1034
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jpobst
force-pushed
the
update-macos
branch
15 times, most recently
from
80ab7b0
to
76e75c7
Compare
OK. I will fix those scripts in the future. |
moljac
approved these changes
Nov 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Mac pool we use
internal-macos12is no longer available. Ideally we could just use the public Azure Pipelines pool, but those machines are underpowered and doubles the (already long!) time taken to build our packages. Switch to the internalVSEng-VSMac-Xamarin-Sharedmac pool already in use bydotnet/androidand MAUI.JavaToolInstaller@0does not seem to work on this image, even though there are many versions of Java SDK already installed on the image. SetJAVA_HOMEto Java SDK 11 so we can build.Additionally, the
tools-executive-oreder-csv-and-markdownCake task does not work on these images because it expectsgradleand other tools to be available in the$PATHwhich they aren't. As we do not consume or ship these files from the build, add a try/catch block to the task so that it does not fail the build if it fails.