* Use minified .js files from submodule in source-build
* Fixup
* Fixup again
* Add check for changes to minified .js files
* Fix typo
* Add doc
* Fix md error
* Update Microsoft.AspNetCore.Components.Endpoints.csproj
* Fix script
* Update submodule
* Print it
* Upload the .js files as part of the build
* Update submodule
For some reason, the new SetupNugetSources does not play well with aspnetcore. No known reason at this point.
Workaround this by removing SetupNugetSources and replacing with commented-out forms of the new templates.
When issues the new templates/scripts have been resolved, will re-enable.
The new version of the powershell script will not place the creds in the nuget.config file, instead it will use standard environment variables. Update the YAML file to use NuGetAuthenticate to avoid a build break that may happen if the credential provider is not available.
* Start converting to 1es pipelines
* Paren
* Try real build
* Self
* Full path
* Fix parens
* Paren again
* Two more selfs
* Fixup
* Try templateContext
* Give it a whirl
* Test
* Fix templateContext
* Fixeroonie
* Fix pool
* Try this
* Fix mac
* Update codesign
* Fix it
* Fix download pattern
* YesBL
* NoBL
* Containers
* Fix containers
* Cleanup
* Pass -publish parameters
https://github.com/dotnet/aspnetcore/pull/54422/files introduced new build script switches for -publish and -no-publish to be compatible with VMR workflows. The aspnetcore CI jobs were passing /p:Publish=true instead of using such a switch. The default value for the new switch if not passed is false, so essentially this turned off publishing for much of aspnetcore. Fix this by not using the msbuild property. Instead, pass the switch. This matches standard arcade repo patterns.
* Add windows publishing argument
* Revert submodules
* Native tools on machine
* Install java via native tools in CI
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.
[main] Update dependencies from dotnet/arcade
- Merge branch 'main' into darc-main-b53c7ee8-482a-44eb-8859-45b8b9099279
- Fix Version.Details.xml
- Fix incorrect shas from manual merge.
- Pass DotNetBuildSourceOnly through to repo tasks build
- Pass DotNetBuildSourceOnly through to repo tasks build
- Merge remote-tracking branch 'upstream/main' into darc-main-b53c7ee8-482a-44eb-8859-45b8b9099279
- Propagate some additional properties
- Unpropagate some additional properties
- Only add if not already added.
- Only add if not already added.
- Keep Duplicates=false.
- Odd
- New approach
- More feeling
- Attempt using 17,8
- Revert "Attempt using 17,8"
This reverts commit 7ccf5160f8.
- Temporarily switch to VS preview queues
- Merge remote-tracking branch 'upstream/main' into darc-main-b53c7ee8-482a-44eb-8859-45b8b9099279
- Revert googletest
* Infrastructure tweaks for unified build
- Use arcade standard prepareMachine to decide whether to kill running processes. Unified build invokes eng/build.ps1 with -ci, as would a user running the build locally. It should not blanket kill the host processes. Pass -prepareMachine in YML files
- if OnlyBuildRepoTasks is passed, don't write a warning that nothing will get built.
* Revert submodules