* Fix code PATs
* Fix feed PATs
* remove gallery commit
* update feed url
* Update to new variable groups
* Fix Variable name
* Fix credential template
* Disable Signing setup in prep stage
* Capture nuget source list
* lock down the firewall
* Add creds to feed switch to allow single switch location
* Use switch from build.psm1
* Use switch template instead of commands
* update to test feed
* disable codeql in jobs where we don't compile
* disable code sign validation for prep
* move capture steps to restore phase to see if it speeds things up
* remove duplicate capture of nuget config
* update test service
* Only build windows test service on windows
* warn when no config is generated
* try to fix test service
* fix web listener refs
* try removing dotnet tool
* update feedname with user info
* update package version that is not found
* try moving failing jobs to restore phase
* allow nuget inset in either phase
* update package ref
* use the right reporoot
* Move everything to restore
* Try adding build phase
* put nuget files in the right place
* move bootstrap into yaml
* remove onebranch agent items from macos build
* switch to environment variable
* bump a couple of packages
* fix formatting
* Fix static analysis issue
* update feed url to test restoring everything
* install the AzFeed cred provider
* fix binlog issues
* Add CI for win-arm64
* Add common function to test for windows arm64
* Update because string where items need investigation
---------
Co-authored-by: Aditya Patwardhan <adityap@microsoft.com>
* Add buildName preview to Jobs and tests
* try other syntax
* give up on task name
* try naming the job again
* use other syntax for variable
* rename and tag build
* Revert "try naming the job again"
This reverts commit b900e1231b.
* conditionally set build name and add tag
* Pass title prefix
* don't add tag when the build is a PR
* use correct variable name
Refactor the `ci.psm1` to publish the code coverage and test packages.
Allow `CodeCoverage` configuration on non-windows.
## PR Context
We plan to run code coverage on Windows, Linux and macOS. These changes are needed to unblock those runs.
The windows-daily build had a bug which caused the packaging builds to be kicked off before tests. This PR fixes the build order.
## PR Context
Fix for failing daily build.
Refactor macOS CI so that tests run in parallel
- Also:
- Fix bootstrap issue where curl was failing for a month (so obviously not needed)
- Change Windows test stages to use PowerShell Core (where we can) to avoid compat issues
## PR Context
This allows running all tests in about the same about of clock time.
I noticed a couple of inconsistencies when reading through the install bash scripts.
- Make documentation for switches consistent over all files.
- Replace all `sed` implementations of `lowercase` with a more maintainable `tr` implementation.
- Set the `OS` variable in every install script, making it so previously unused checks are actually used.
- Exit with a non-zero exit code when the script reaches an illegal state.
## PR Context
A lot of people, including myself, read the install scripts before executing them. While doing so I noticed they contained inconsistencies. For example, certain flags you can pass to the install script were either undocumented or had an incorrect description. This PR fixes some of these inconsistencies, which should make them easier to maintain and easier to read.
Co-authored-by: Travis Plunk <github@ez13.net>
This removes some of the last mentions of the AppVeyor name. Don't change the title, we don't want the word to appear in the CLs
Also problem: the last references are in the changelogs but I don't want to modify them without committee approval.
## PR Context
it was removed, #8686
Split Windows CI into the following Jobs
1. Combine Build and xUnit, which published build artifact
1. Elevated CI tests
1. Unelevated CI test
1. Elevated everything else tests
1. Unelevated everything else tests
1. Package build and test
1. Verify xUnit result
## PR Context
Before this test:
- A CI run would take ~14 minutes
- A Feature run would take ~30 minutes
After this change, it always runs all tests and takes ~20 minutes.
Job `Unelevated everything else tests` is the long poll, taking ~4 minutes longer than the next shortest job. We should be able to get this back down to ~15 if we split that test job somehow.
