Skip to content

Install java via native tools in CI #54421

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

Merged
merged 8 commits into from
Mar 13, 2024

Conversation

mmitche
Copy link
Member

@mmitche mmitche commented Mar 7, 2024

The VMR doesn't have Java installed globally on the machines, but it does have it in the native tool cache like other CI machines. This PR updates the build scripts to use the native tool cache to install Java in CI builds. I've also updated to 11.0.22 (vs. the .3 version from 2019) and the script used to pull this from native tool assets storage account.

The VMR doesn't have Java installed globally on the machines, but it does have it in the native tool cache. This PR updates the build scripts to use the native tool cache to install Java in CI builds. I've also updated to 11.0.22 (vs. the .3 version from 2019) and the script used to pull this from native tool assets.
@mmitche mmitche requested review from wtgodbe and a team as code owners March 7, 2024 21:14
@ghost ghost added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Mar 7, 2024
@mmitche
Copy link
Member Author

mmitche commented Mar 7, 2024

@@ -200,7 +200,8 @@ stages:
steps:
- script: ./eng/build.cmd
-ci
-prepareMachine
-prepareMchine
-nativeToolsOnMachine
Copy link
Member

Choose a reason for hiding this comment

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

Spacing is off here

@@ -12,8 +12,6 @@
"$(MicrosoftNETCoreBrowserDebugHostTransportVersion)"
]
},
"Git": "2.22.0",
Copy link
Member

Choose a reason for hiding this comment

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

Why remove git?

Copy link
Member Author

@mmitche mmitche Mar 7, 2024

Choose a reason for hiding this comment

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

This doesn't do anything that I can tell. Do you know of any place that reads this? Btw last updated in 2019?

@mmitche
Copy link
Member Author

mmitche commented Mar 7, 2024

This needs a tweak or two.

@amcasey
Copy link
Member

amcasey commented Mar 7, 2024

Do we need something similar for wasm-tools?

Edit: ignore me - this is apparently known and the new requirement is being reverted. Out of curiosity, would the fix look like this, if we were going to install it?

@mmitche
Copy link
Member Author

mmitche commented Mar 11, 2024

This needs a tweak or two.

Because the native tools are laid out in a weird way...this doenst' work locally...i'll need to disable native tools installs unless the native tools are on the machine

@mmitche mmitche closed this Mar 12, 2024
@mmitche mmitche reopened this Mar 12, 2024
@dotnet-policy-service dotnet-policy-service bot added this to the 9.0-preview3 milestone Mar 12, 2024
@mmitche mmitche closed this Mar 12, 2024
@mmitche mmitche reopened this Mar 12, 2024
@mmitche mmitche enabled auto-merge (squash) March 12, 2024 23:05
@mmitche mmitche merged commit 1aa1c5b into dotnet:main Mar 13, 2024
@MackinnonBuck
Copy link
Member

@mmitche, we've been seeing a lot of failures in main since this merged:

Could not find the JDK. Either run D:\a\_work\1\s\eng\scripts\InstallJdk.ps1 to install for this repo, or install the JDK globally on your machine (see D:\a\_work\1\s\eng\..\docs\BuildFromSource.md for details).

Do we need to revert this? Or do a follow-up?

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.

4 participants