use locally cached tpn files #8330
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
majastrz
commented
Sep 10, 2022
| GenerateNoticeUseLocalFile: false | ||
| GenerateNoticeUpdateLocalFile: true | ||
|
|
||
| steps: |
majastrz
force-pushed
the
majastrz/local-notice-files
branch
from
b1dc569 to
a77df71
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our GH builds are currently using an external API to generate third party notice (tpn) files. The API is somewhat flaky which is causing transient build failures. To mitigate the problem, we will use locally checked in files for GH builds with an independent build job that will run on a schedule to generate the TPN files using the API and create a PR to check them in. ADO builds will continue to rely on the API to generate TPN files.
Here's a sample PR created by the new scheduled build job: #8329