* Fix conflict
* Use native tools on machine
* Fix SignalR Java POM to include description
* Try stream8
* New pool
* No git
* Maybe change the order
* Add newline at end of global.json file
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Brennan <brecon@microsoft.com>
Co-authored-by: Matt Thalman <mthalman@microsoft.com>
#### AI description (iteration 1)
#### PR Classification
Configuration update.
#### PR Summary
This pull request updates the token timeout configuration in the build pipeline.
- `.azure/pipelines/jobs/default-build.yml`: Added `expiryInHours` parameter with a value of 2 to the `enable-internal-runtimes.yml` template.
#### AI description (iteration 1)
#### PR Classification
Code enhancement to regenerate runtime tokens before building installers.
#### PR Summary
This pull request ensures that runtime tokens are regenerated before building the installers to avoid hitting the hour timeout.
- `.azure/pipelines/ci.yml`: Added a step to regenerate runtime tokens before the installer build process.
- import the variable template
- use the two variables it provides wherever we name the pool
- future release branches will now automatically switch to the -Svc pools
* Add CodeQL3000 run to aspnetcore-ci-official
- add new schedule for a weekly run
- add top-level parameter enabling CodeQL3000 in manual builds
- add `enableSBOM` and `variables` parameters in default-build.yml
- add a separate job w/ CodeQL3000 tasks included in build steps; run this job alone
- use the new default-build.yml parameters
- set `$(UseSharedCompilation)` to `false` to ease analysis
- tag CodeQL3000 runs
- add a tsaoptions.json file
- cribbed values from our eng/sdl-tsa-vars.config file
nit: Unconditionally disable the auto-injected component governance build step
- job.yml inserts the task where we need (unless overridden)
- should affect most of our pipelines though not a few post-build jobs
- as we saw in #43028, binary logs no longer include all environment variables by default
- this change captures the environment variables not visibly referenced in our projects etc.
- fix avoids a need to add the override later to debug an issue, at the cost of larger .binlog files
- {lots of different SDK versions tried}
- Validate DataProtection custom algorithm has a constructor
- Additional fixes
- Suppress IL2121
- Fix NoWarn overrides
- Update LinkabilityChecker.csproj
- Update WasmLinkerTest.csproj
- Bump SDK version yet again
- Hack to stop using `msbuild` server
- please open an issue to keep trying to remove this
- Disable msbuild server for source-build job
Co-authored-by: Steve Sanderson <SteveSandersonMS@users.noreply.github.com>
Co-authored-by: Chris Ross <chrross@microsoft.com>
Co-authored-by: Tanay Parikh <TanayParikh@users.noreply.github.com>
Co-authored-by: James Newton-King <james@newtonking.com>
Co-authored-by: Sébastien Ros <sebastienros@gmail.com>
Co-authored-by: Doug Bunting <6431421+dougbu@users.noreply.github.com>
Co-authored-by: Safia Abdalla <safia@microsoft.com>
* Specify the current agent demands and VS version
- we require VS2022 to build native code these days
- Core-Eng really likes `1es-windows-2019[-open]` 😀
* !fixup! Remove extra `$(WindowsTargetPlatformVersion)` settings
- set in Cpp.Common.props
- was incorrect in common.props and led to requiring two Windows SDK versions
* Remove extra aspnetcore-components-e2e build tasks
- remove `isTestingJob` parameters in YAML
- controls `PublishTestResults@2` tasks that all fail
- add comments in components-e2e and Helix jobs about "missing" `isTestingJob` parameters
nits:
- remove mention of non-existent `Windows_Templates_Test` job
- use `testResultsFormat` input name for consistency (alias of `testRunner`)
* Skip useless test publications
- add `enablePublishTestResults` parameter to default-build
- quarantined-pr contains test jobs but all publish their tests explicitly
- do not attempt to publish TRX files
nit: simplify a YAML snippet
- `parameters.buildDirectory` is never empty (has a default)
* Eval two conditions during template expansion
- remove jobs that will never execute from UI
* Address feedback
- rename `parameters.isTestingJob` to `isAzDOTestingJob`
- remove `condition`s about `variables.DotNetFinalVersionKind`
- variable has not been used in a _very_ long time
- document `parameters.isAzDOTestingJob` and `enablePublishTestResults`
* !fixup! Add comment for eb9e4c9ea4b9 change
- explain how to test site extension changes
* !fixup! Simplify one more expression
- missed this one in fc286da973
- #33534
- copy source-index-stage1 template into ci.yml and split steps in two:
- current template not well suited to reuse a binary log from another job
- first, process Windows_arm_build binary log in that job
- align binary log with source-indexing tool support i.e. always use Windows
- much faster than Windows x64/x86 build
- provides another binary log, even in internal builds
- second, do source index upload after other jobs
- do not update https://source.dot.net/ from failed builds
- add `testSourceIndexing` parameter
- use 1ES agent for source-index upload
- `windows-latest` might work but prefer to protect binary log
nits:
- remove unnecessary backslashes in the Linux_x64_build job's `script`s
- instead separate commands with a semicolon
- confirm test build success before BAR updates in manual builds
- merge a couple of `in(...)` expressions
- do not set parameters to their default values
- do not set `installJdk` except in Windows jobs (ignored otherwise)
- remove unused `continueOnBuildError` and `installTar` parameters
- components-e2e-tests.yml no longer needs `continueOnBuildError`
- remove confusing `SkipTests` conditions in test-only pipelines
nits:
- sort parameters to align with documentation
- provide defaults for undocumented parameters (reduce searching)
- follow up to 0d0103b4c0
- `COMPlus*` variables were uppercased and `dotnet` ignored them on Linux / macOS
- only upload dumps in `failed()` jobs
- use scripts to avoid more YAML complications and avoid empty artifacts
- `$use_global_nuget_cache` and `$useGlobalNuGetCache` have default values in our pipelines
- therefore, cache is always within `$(System.DefaultWorkingDirectory)` and should not exist at job start
* Updates npm dependencies to their latest versions.
* Standardizes build process for our JS dependencies on webpack 5 with babel, etc.
* Updates dependencies for the auth packages to their latest versions.
* Fixes test assets so that they can be run locally.
* Clean out Ubuntu 16.04 testing
- use Ubuntu 18.04 agents for testing in Docker containers on Helix
nits:
- clean up a few old mentions of Centos and Fedora testing
- fix `%(Platform)` metadata for OSX `@(HelixAvailableTargetQueue)` items
- don't mention unused internal queues in `$(TestDependsOnPlaywright)` update of `$(SkipHelixQueues)`
- sort remaining queues alphabetically in `$(SkipHelixQueues)`
William Godbe
Matt Mitchell
Alexander Köplinger
Igor Velikorossov
Brennan
Doug Bunting
Anthony Tossell
Chris Ross
Bruno Oliveira
Stephen Halter
Alex Perovich
Mackinnon Buck
Matt Galbraith
Steve Sanderson
Tanay Parikh
Javier Calvarro Nelson
Jon Fortescue
Hao Kung
Sébastien Ros