The old version of TSA automatically added the branch name to the database, which was kind of wasteful since new databases were created from each non-main branch used for a signed test build. The new version of TSA uses the same database name for all branches, which means that builds from any branch could create noise in the production version. To solve both problems, this PR restricts the TSA upload to just the main branch. All TSA artifacts are created as usual, but the upload task gets skipped. This is based on the method shown here.
Details
Note: This is the analog of https://github.com/microsoft/accessibility-insights-windows/pull/1578
The old version of TSA automatically added the branch name to the database, which was kind of wasteful since new databases were created from each non-main branch used for a signed test build. The new version of TSA uses the same database name for all branches, which means that builds from any branch could create noise in the production version. To solve both problems, this PR restricts the TSA upload to just the main branch. All TSA artifacts are created as usual, but the upload task gets skipped. This is based on the method shown here.
The Validation build skips both TSA uploads:
Motivation
Maintain a single clean copy of the TSA database for the repo.
Context
Pull request checklist