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

Use MacOS-13 in CI #58465

Merged
merged 13 commits into from
Oct 21, 2024
Merged

Use MacOS-13 in CI #58465

merged 13 commits into from
Oct 21, 2024

Conversation

wtgodbe
Copy link
Member

@wtgodbe wtgodbe commented Oct 16, 2024

No description provided.

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Oct 16, 2024
@wtgodbe wtgodbe marked this pull request as ready for review October 16, 2024 19:05
@wtgodbe wtgodbe requested a review from a team as a code owner October 16, 2024 19:05
@wtgodbe
Copy link
Member Author

wtgodbe commented Oct 16, 2024

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@@ -116,9 +116,9 @@ public Single<HttpResponse> send(HttpRequest httpRequest, ByteBuffer bodyContent
case "POST":
RequestBody body;
if (bodyContent != null) {
body = RequestBody.create(MediaType.parse("text/plain"), ByteString.of(bodyContent));
body = RequestBody.Companion.create(ByteString.of(bodyContent), MediaType.parse("text/plain"));
Copy link
Member

Choose a reason for hiding this comment

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

@wtgodbe
Copy link
Member Author

wtgodbe commented Oct 21, 2024

/backport to release/9.0

@wtgodbe
Copy link
Member Author

wtgodbe commented Oct 21, 2024

/backport to release/8.0

Copy link
Contributor

Started backporting to release/9.0: https://github.com/dotnet/aspnetcore/actions/runs/11443032159

Copy link
Contributor

Started backporting to release/8.0: https://github.com/dotnet/aspnetcore/actions/runs/11443034354

@github-actions github-actions bot mentioned this pull request Oct 21, 2024
11 tasks
Copy link
Contributor

@wtgodbe backporting to release/8.0 failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Applying: Use MacOS-13 in CI
Applying: Gradle 6.9
Applying: Update gradle-wrapper.properties
Applying: Update gradle-wrapper.properties
Applying: Update build.gradle
Applying: Update build.gradle
Applying: Update build.gradle
Applying: Update build.gradle
Applying: Update build.gradle
Applying: Update build.gradle
Applying: Update build.gradle
Applying: Fixup gradle
Using index info to reconstruct a base tree...
M	global.json
M	src/SignalR/clients/java/signalr/core/build.gradle
Falling back to patching base and 3-way merge...
Auto-merging src/SignalR/clients/java/signalr/core/build.gradle
Auto-merging global.json
CONFLICT (content): Merge conflict in global.json
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0012 Fixup gradle
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

Copy link
Contributor

@wtgodbe an error occurred while backporting to release/8.0, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

@wtgodbe wtgodbe merged commit 5bfe483 into main Oct 21, 2024
27 checks passed
@wtgodbe wtgodbe deleted the wtgodbe/Mac13 branch October 21, 2024 20:05
@dotnet-policy-service dotnet-policy-service bot added this to the 10.0-preview1 milestone Oct 21, 2024
@@ -24,7 +24,7 @@
"xcopy-msbuild": "17.1.0"
},
"native-tools": {
"jdk": "11"
"jdk": "11.0.24"
Copy link
Member

Choose a reason for hiding this comment

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

@wtgodbe this change broke the entire VMR now that images got updated to a newer version of the jdk. This already happened once in the past which is why we made this change: 4a3afe3

Can you please describe why the minor and patch versions were necessary to be added here?

cc @mmitche

Copy link
Member

Choose a reason for hiding this comment

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

Clean local dev is broken if you use a non-specific version
#58457

Copy link
Member

@ViktorHofer ViktorHofer Jan 9, 2025

Choose a reason for hiding this comment

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

I see, thanks for sharing the details.

Arcade offers scripts to install native tools which support defining just a major version or even "latest": https://github.com/dotnet/aspnetcore/blob/main/eng/common/init-tools-native.ps1

Any reason why you can't use those? The problem with the hardcoded version is that it breaks whenever the CI images get updated. I.e. right now all aspnetcore builds should be broken. See dotnet/sdk#45822

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 don't see any reason why we can't - I'd actually prefer it. Do we just need to add a pre-step in CI that runs the script?

Copy link
Member Author

Choose a reason for hiding this comment

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

We used to install the JDK manually ourselves w/ https://github.com/dotnet/aspnetcore/blob/main/eng/scripts/InstallJdk.ps1, but stopped with #54421. I was under the impression we had to use whatever was pre-installed on the build machine/in the VMR tool cache

Copy link
Member

@ViktorHofer ViktorHofer Jan 9, 2025

Choose a reason for hiding this comment

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

I was under the impression we had to use whatever was pre-installed on the build machine/in the VMR tool cache

Yes, we need to use what's preinstalled on the machine. The Arcade script doesn't help downloading assets, it just helps finding the locally installed tool and promote it to PATH.

Let's move that discussion to dotnet/source-build#4816

captainsafia pushed a commit that referenced this pull request Feb 11, 2025
* Use MacOS-13 in CI

* Gradle 6.9

* Update gradle-wrapper.properties

* Update gradle-wrapper.properties

* Update build.gradle

* Update build.gradle

* Update build.gradle

* Update build.gradle

* Update build.gradle

* Update build.gradle

* Update build.gradle

* Fixup gradle

* Apply suggestions from code review

---------

Co-authored-by: Brennan <brecon@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants