-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run Flank in GitHub Action #2304
Comments
|
I'll reach out privately because I would like to learn more about this... |
OK, I'm learning more about this, so there are 1-2 problems, here:
|
Note to future self: The following is just a Warning and it already always appears and is no problem:
This is NOT related to and not NOT the root cause of problems such as the following:
|
The 403 above is fixed by granting the "Editor" role to the SA, as per https://firebase.google.com/docs/test-lab/android/continuous. (Note to future self: It seemed like that it didn't seem to work when I added the "Editor" role to an existing SA, but worked if I created a new one to which I added it at creation time? I'm probably just very confused about the GCP Console; using With this I'm half way there, but still fails at the end:
This is strange, because the Editor role should have the |
The (2nd) 403 above is because there are actually 2 separate GCP projects involved here:
I'll follow up internally at work to get access sorted out. |
I would like to explore if it's possible to run (trigger?) Flank (https://flank.github.io/flank/) in the GitHub Action (which now works fine otherwise),
i.e.
./gradlew :engine:runFlank
etc.as in https://github.com/google/android-fhir/blob/master/kokoro/gcp_ubuntu/kokoro_build.sh
If this works, then I'm not sure this project still needs the Google internal only Kokoro infrastructure? (Thus "fixing" e.g. #2300 or #2297 et al.)
This would, to me, lead to a simplification of this project's (to me, seemingly) "complex" CI infra.
The text was updated successfully, but these errors were encountered: