Skip to content

Everytime the jdk gets updated on build machines, VMR builds break and need a manual update in aspnetcore #4816

Closed
@ViktorHofer

Description

@ViktorHofer

See dotnet/sdk#45822 for more details. I wonder if we really need to specify the exact jdk version that must be available on the build agent. As long as we do that, we keep breaking the VMR and aspnetcore builds with every update.

Arcade has support for finding tools on the machine and promoting them to PATH by using "latest" as the version in global.json. It doesn't attempt to download or install it (anymore) - it must already be available. But that's a necessity anyway for our build agents that are managed by dnceng and our docker images that we control.

Based on dotnet/aspnetcore#58465 (comment), the aspnetcore team still wants a local option to install a version of the jdk, i.e. by invoking a script.

cc @mmitche @wtgodbe @BrennanConroy @akoeplinger

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions