Onboarding.md

Onboarding onto Arcade

• Onboard onto the arcade SDK, which provides templates (building blocks) for interacting with Azure DevOps, as well as shared tooling for signing, packaging, publishing and general build infrastructure. (Here's a video of a walkthough which might help too)

  Arcade SDK onboarding

  1. Add a global.json.
  2. Add (or copy) Directory.Build.props and Directory.build.targets.
  3. Copy eng\common from Arcade into repo.
  4. Add (or copy) the Versions.props and Version.Details.xml files to your eng\ folder. Adjust the version prefix and prerelease label as necessary.
  5. Add dotnet-core feed to NuGet.config.
  6. Must have a root project/solution file for the repo to build.
  7. Additional package feeds can be added to the eng\Version.props file, e.g.

     <PropertyGroup>
       <RestoreSources>
         $(RestoreSources);
         https://www.myget.org/F/nugetbuild/api/v3/index.json;
         https://dotnet.myget.org/F/dotnet-web/api/v3/index.json
       </RestoreSources>
     </PropertyGroup>
     

  Using Arcade packages - See documentation for information on specific packages.

• Move out of .NET CI and into our new Azure DevOps project (https://dev.azure.com/dnceng/public) for your public CI. - See Onboarding Azure DevOps.

• Move out of the devdiv Azure DevOps instance (https://dev.azure.com/devdiv/ or https://devdiv.visualstudio.com) and into the internal project for (https://dev.azure.com/dnceng/internal) internal CI and official builds. - See Onboarding Azure DevOps and Moving Official Builds from DevDiv to DncEng.

• Onboard onto dependency flow (Darc). - See Dependency Flow Onboarding.

• Use Helix for testing where possible - See Sending Jobs to Helix

Which branches should I make these changes in?

Prioritize branches that are producing bits for .NET Core 3. Given the extended support lifecyle for .NET Core 2.1, backporting infrastructure to .NET Core 2.1 release branches is desired, but .NET Core 3 branches should go first.