- Move mgmt tools to mgmtci.proj and not in dotnet.proj
- update mgmt package project to use project instead of nuspec
So that we can have a unique build each time.
For now to build the mgmt tools you need to specific mgmtci.proj
from the build queue when starting the build.
1. azure-sdk-for-net
2. Fluent .NET SDK
3. Multi-Api-Sdk
Pre-req:
Install dotnet SDK 2.2.300 prior using toolset
https://dotnet.microsoft.com/download/dotnet-core/2.2
This PR contains following functionality:
1. All build tools wrapped as nuget package (no longer have to download prior to build)
2. Toolset is .NET Core based. Same set of build targets will work cross platform. Tested on mac.
3. Ability to detect PR validation CI runs and find appropriate SDKs to build based on the PR
4. Based on the SDK, it detects appropriate test projects within the same scope
5. Supports parity build scenarios that worked earlier.
6. This PR currently supports all parity searching projects scenarios based on following criteria
6.1 Search projects when no scope is provided
6.2 Search projects when scope is provided (partial scope)
6.3 Search projects when fully qualified scope dir path is provided
6.4 Search projects when ProjectType is specified
6.5 Search projects when ProjectCategory is specified (not extensively tested/checked for data plane project types, as data plane decided not to participate in this workflow)
6.6 Search projects when Include/Exclude tokens are specified at command line
6.7 Search project honoring exclusion/inclusion settings specified in project files (swagger to SDK scenarios)
7. Ability to get KeyVault secrets.
8. KV auth based on SPN (SPN has to be configured based on new KV)
9. Added tests
Wes Haggard
shahabhijeet