Update README.md#19
Conversation
• Update Integration Testing directions to match updates made to GoogleUtils's README. • Added some syntax highlighting to existing code blocks.
| * Run Firebase CI by waiting until next nightly or adding a PR that touches `Gemfile`. | ||
| * On google3, copybara and run a global TAP | ||
| ```console | ||
| third_party/firebase/ios/Releases/run_copy_bara.py --directory GoogleDataTransport --branch main |
There was a problem hiding this comment.
The run_copy_bara.py script may not work for GDT. Here is the last command I used for GDT:
/google/data/ro/teams/copybara/copybara third_party/firebase/ios/Releases/GoogleDataTransport/copy.bara.sky --piper-description-behavior=OVERWRITE --destination-cl=367099297 gdt
So more investigation is needed here and we likely want to make gdt consistent with GoogleUtilities, but not necessary for this PR
There was a problem hiding this comment.
I'll replace the current command with this one for now...
There was a problem hiding this comment.
Figured out how to do this in g3 and updated docs accordingly in latest commit
| git tag CocoaPods-{version} | ||
| git push origin CocoaPods-{version} | ||
| ``` | ||
| * Push the podspec to SpecsStaging |
There was a problem hiding this comment.
Might be worth writing that it should push to SpecsStaging if the GDT is intended to launch before or with the next Firebase release. Otherwise it should push to SpecsDev
There was a problem hiding this comment.
I added collapsible sections to hopefully make the reader's actions align with their intent and prevent accidental pod repo pushes to the wrong repo
There was a problem hiding this comment.
@paulb777 Should something similar be done on the GoogleUtils repo as well?
Coverage ReportAffected SDKs
Test Logs |
|
I'm not sure if GDT requires using the |
I'm not sure it needs them, but we often add |
3 participants
• Update Integration Testing directions to match updates made to GoogleUtils's README.
• Added some syntax highlighting to existing code blocks.