new signing pipeline (part1)

[TimothyMothra]

#2475.

This PR introduces the new pipelines for our new signed builds.
I need this on the main branch to test some of the compliance settings.

Please review screenshots below for a description of the pipeline output.

A follow up PR will:

• refactor/normalize some of the scripts and settings.
• resolve all compliance issues.

Changes

• Creating three new pipelines
  • "Buddy" will be used in PR validation.
  • "Official" is for signing the AI SDK
  • "Official Redfield" is for signing the AI SDK w/ Redfield build flag
• Creating new *.cmd scripts.
  FYI: pipelines cannot have inline scripts and must use external files.
  • i've numbered these scripts in order to sort them according to which "build stage" they will be used.

Checklist

• I ran Unit Tests locally.
• CHANGELOG.md updated with one line description of the fix, and a link to the original issue if available.

For significant contributions please make sure you have completed the following items:

• Design discussion issue #
• Changes in public surface reviewed

The PR will trigger build, unit tests, and functional tests automatically. Please follow these instructions to build and test locally.

Notes for authors:

• FxCop and other analyzers will fail the build. To see these errors yourself, compile localy using the Release configuration.

Notes for reviewers:

• We support comment build triggers
  • /AzurePipelines run will queue all builds
  • /AzurePipelines run <pipeline-name> will queue a specific build

[TimothyMothra]

As of commit c6cfebc we have three builds....

Buddy

The buddy build does not permit signing and will eventually run with all PRs.

The log correctly identifies itself

The output NUPKGs are not signed.
The contained DLLs are not signed.

TODO

• change build params to include build number. This is to distinguish between "official" builds.

Official

The official build uses signing.

The log correctly identifies itself

The output NUPKGs are signed.
The contained DLLS are signed.

Official Redfield

This is an official build, which uses signing.

The log correctly identifies itself

The output NUPKGs are signed.
The contained DLLs are signed.

TODO

• should the package name include "redfield" instead of "beta"?

[TimothyMothra]

Fixed Redfield, now has correct package name.

[TimothyMothra]

fixed package name for Buddy build:

[reyang]

nit: many of these commands (e.g. dotnet) are platform independent, consider getting rid of the cmd file and make it self-contained.

e.g. https://github.com/open-telemetry/opentelemetry-dotnet/blob/66d2621170c614313c81fc82e4f6c79218244974/.github/workflows/linux-ci.yml#L44

[TimothyMothra]

I would have GREATLY preferred this approach.
I went to office hours to ask this exact question. OneBranch does not permit in-line scripts as a rule!

In all of our github builds, i'm doing everything in-line:

ApplicationInsights-dotnet/.github/workflows/build-and-test-BASE.yml

Line 47 in e8eb520

run: dotnet build ./BASE/Microsoft.ApplicationInsights.sln --configuration Release --no-restore

[reyang]

LGTM with some suggestions.