This pullrequest adds a definition for an expanding and contracting
build that will be used to replace all `js - <service> - ci` build
definitions in the `public` devops project. This is an overall package
selection change, where we find the targeted packages using
`Save-Package-Properties.ps1` primarily. Analyze checks have also been
updated to honor this new selection methodology, rather than the hardcoded
artifactslist.
Only `js - pullrequest` will actually honor the expand and contract for
the packages that were changed in the PR. Meanwhile the `internal`
versions of the `service`-specific definitions will still exist, still
select packages for the service directory, and still be used to release
as normal.
`js - pullrequest` will run _alongside_ the existing builds for a short
period while we identify any outstanding bugs or collection adjustments.
After we're happy, we'll disable all public js builds in favor of the
single `js - pullrequest` build.
---------
Co-authored-by: Ben Broderick Phillips <bebroder@microsoft.com>
* Add CompatibleConvertFrom-Yaml to common Package-Helpers
* Add CI artifact parsing to Save-Package-Properties, now each individual packageinfo.json file contains the relevant ci artifact lines for the package. This short circuits needing to re-parse this information in common checks.
---------
Co-authored-by: Scott Beddall <scbedd@microsoft.com>
This change is necessary to match change in Update-DocsMsMetadata.ps1
made in [this azure-sdk-tools
PR](https://github.com/Azure/azure-sdk-tools/pull/7951). The
Get-javascript-DocsMsDevLanguageSpecificPackageInfo function is the
implementation of the GetDocsMsDevLanguageSpecificPackageInfoFn. This is
something that should have been called all the time but because
javascript was the only language using this, Update-DocsMsMetadata.ps1
was only calling this if the packageInfo file's DevVersion was set.
Because this needs to be called all the time, if it's defined for a
given language, and javascript only needs process if the DevVersion is
set, move that check to the implemented function.
* Remove @azure/core-asynciterator-polyfill usage
* Remove @azure/core-asynciterator-polyfill usage
* Remove from workspace too
* Remove from core artifacts list
* Make eslint happy
* Fix more eslint errors
Co-authored-by: Jeremy Meng <yumeng@microsoft.com>
* Add ToC Generation script and wire up to docindex.yml for testing
Add Docs-ToC.ps1
Remove eng/scripts/docs from .gitignore but keep filtering other docs/ folders
Also checkout packages-legacy.json in sparse checkout
Also check out docs-ref-mapping/
Use -toc-test branch for demo
Review feedback
Review feedback
Remove unnecessary comment
Undo working changes
Add extension point to update the ToC before output
Undo changes to demo set-daily-docs-branch-name.yml
Check for FileMetadata before accessing it
Add ability to artbitarily nest packages in the 'Other' service.
Add comments from review feedback
Add plugin nodes
* Revert unnecessary changes to eng/common
* Review feedback
* Remove automatic ToC generation from main
* Set-StrictMode
* Remove Release-DocsMsDocs.ps1
* Use original syntax
* Add update cspell.json, add exceptions to opt out services with spelling errors
Turn on spell check failures in CI
Add opted out services
Update words list, sort, fix syntax
Add more exceptions
progress
Use current cspell.json
* Add spell check enforcement for public API surface area
* Exclude checking spelling in sdk/test-utils
* Add automation for spell checking the public API surface to aggregate-reports and analyze job
* Remove -ServiceDirectory parameter from aggregat-reports
* Add engsys spelling exceptions
* Do not fail analyze step on spelling errors in modified files
* npx
* Opt out the generated packages
* Add spell checking and failure for public API surface (pre opt-out)
* Improve error logging and spelling error report
* Pin cspell version
* Use Invoke-Cspell.ps1 to pin cspell version
* Use Invoke-Expression and multiple --package entries to pin cspell and dictionary to expected version
* Use npm exec strategy for Invoke-Cspell.ps1
* Move Set-Location
* Use simplified Get-ChildItem
* Apply suggestions from code review
Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>
* Add exclusions for packages which have cspell spelling error detections
* Update eng/common/spelling/Invoke-Cspell.ps1
Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>
* Variable naming
* Add ability to use LICENSE[.txt] file instead of generating a file, add MSRC to words list
* Get NPM info
* Upgrade NPM
* Parentheses
* Variables
* Remove spelling error temporarily
* Revert "Remove spelling error temporarily"
This reverts commit dd681aca1203e364f36ca82d3acf0bd03d27e20c.
* Attempt to fix link
* Aggregate reports should use version of npm compatible with Node 10.x
* Perform Node/NPM upgrades manually in aggregate-reports.yml, put Node/NPM upgrade directly into check-spelling.yml template in eng/common so it gets used everywhere
* Remove redundant use-node-version.yml
* Move NPM version switch to fix aggregate-reports
* Do not mutate local NPM environment
* Revert incorrect proposed changes to eng/common
* Clean up opted out entries, exclude arm-* which are already excluded in another glob
* Globals template is not needed because use-node-version.yml specifies a node version to use
* Use use-node-version.yml
* Use new exclusion globs
Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>