Publish artifacts to S3 in packaging build

[zacharycmontoya]

Improve the packaging Azure DevOps pipeline for building/deploying/testing master:

• Run the packaging pipeline on each commit to master
• Upload the following files to s3 for testing:
  • datadog-dotnet-apm-${MAJOR_MINOR_PATCH_WITH_PRERELEASE}-x64.msi
  • datadog-dotnet-apm-${MAJOR_MINOR_PATCH}-amd64.deb
  • index.txt that has supplementary information about the latest commit

The index.txt file contains the branch, SHA, filename (or wildcard) for installing, and the author:

zach/reliability-env/packaging
4f7ebb128af5b1ec5dea07c31e73ab2dd73cfded
datadog-dotnet-apm-1.15.0-*
zach.montoya@datadoghq.com

@DataDog/apm-dotnet

[lucaspimentel]

If I understand correctly, this will keep uploading new packages with version 1.15.0 until we bump the version number. Isn't this going to be an issue? Should we use the output from GitVersion or the commit hash to generate a unique version number for each master commit?

[zacharycmontoya]

Your understanding is correct: until we increase the version number, the artifacts will overwrite on each publish. I don't see this as an issue because we only care about measuring one non-Release commit at a time, which is the head of master. Am I missing something?

[lucaspimentel]

Nope, just checking. Thanks!