Граф коммитов

6 Коммитов

Автор SHA1 Сообщение Дата
Doug Bunting 59e5920d69
Use Arcade's pool-providers.yml (#46493)
- 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
2023-02-08 18:49:01 -08:00
Anthony Tossell c37ee916d1
Changed docs.microsoft.com links to learn.microsoft.com Issue: #44175 (#46206)
Updated links from microsoft.docs.* to microsoft.learn.*
- fixes #44175
- also remove version info from the URIs
2023-01-24 02:07:15 +00:00
Doug Bunting 1e2d80b290
Get richnav.yml building again (#40729)
- correct build.cmd location
- generally, align richnav.yml with ci.yml
  - ignore signing, internal download args, and publish args
  - perform native build w/o rich nav and don't do installers build; both fail
- disable pipeline in PR validation
  - also remove irrelevant trigger branches

nits:
- correct name of one build step in ci.yml
- don't bother setting `$(EnableRichCodeNavigation)` or `$(OnlyPackPlatformSpecificPackages)` to `true`
  - job.yml sets `$(EnableRichCodeNavigation)` variable and `msbuild` will find that in environment
  - `$(OnlyPackPlatformSpecificPackages)` is not relevant in this pipeline; not packing
2022-03-18 19:07:04 -07:00
Doug Bunting 55c92f4e71
Cleanup YAML parameters and settings (#37186)
- 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)
2021-10-01 21:53:48 -07:00
Tanay Parikh 3ffb13be89
Update richnav pipeline trigger branches (#32280) 2021-04-29 22:37:50 +00:00
Jessica Petty a7437be214
Add Rich Nav specific pipeline, temporarily add to ci for testing (#26822)
* Add Rich Nav specific pipeline, temporarily add to ci for testing
* Add Rich Code Navigation feed to Nuget.config
* Temporarily disable package reference restrictions
* Try running Rich Nav task directly
* Fix typo
* Temporarily update rich nav task to verify successful run
* Remove Rich Nav code from regular CI
* Remove unnecessary args from Rich Nav build, add language variable
* Apply fixes to Rich Nav pipeline
* Remove specific binary log build args, stop disabling package reference restrictions
* HACK HACK HACK replace existing CI with rich nav CI to test
* Begin publishing artifacts to start debugging empty files
* Explicitly set environment variable for rich navigation
* Publish binlogs
* Try manually updating arcade sdk to get new rcn package
* Upload logs even if we've failed (hopefully they exist!)
* Add RCN task to run on succeeded or failed to see what happens!
* Remove parameters that aren't defined
* Final rich nav test/assertion
* Replace normal CI and finalize Rich Nav CI script
2021-02-25 12:27:06 -08:00