-
Notifications
You must be signed in to change notification settings - Fork 3
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
Missing local.properties Step in GitHub Actions Workflows #127
Comments
You can check this with someone with knowledge in DevOps. As Android developer, this is out of my scope. c.c.: @nelsonwilches @dzuluaga @mariomonteroencora @teban1288 |
I'll redirect this to @nelsonwilches for validate who will work on this |
It's a couple of line of code. Could you take a look at how the OMH Maps does it? Thanks |
Currently, github actions on storage are basically a copy-paste of the ones defined on auth and maps. The only difference is the one done due to issue #97 (PR #102) Far away from that, i don't have knowledge about CI. So, @nelsonwilches will redirect this to an appropiate person. c.c.: @dzuluaga @nelsonwilches @mariomonteroencora @teban1288 |
Okay. But, for the record, you're already doing it on the on_pull_request.yml. It's just missing in the other yml files. |
Checked this with @hans-hamel and opened a PR: #130 Once merged, please let us know if this solves the issue |
PR merged c.c.: @dzuluaga @nelsonwilches @mariomonteroencora @teban1288 |
It works. Thanks! |
GitHub Actions workflows for OMH Storage API, OMH Storage API Drive GMS Implementation, and OMH Storage API Drive non-GMS Implementation are failing due to the absence of the
local.properties
setup step in the workflow YAML files. This step is essential for configuring environment variables and SDK paths.Proposed Solution:
Add the necessary step to set up the
local.properties
file in the workflow YAML files to resolve the build failures.Reference Run:
GitHub Actions Run
Please address this issue promptly to enable successful builds and contributions. Feel free to reach out for any additional information.
The text was updated successfully, but these errors were encountered: