Skip to content
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

CI/CD system doesn't resolve environment variables #65

Open
MaxMichel2 opened this issue Jun 27, 2023 · 1 comment
Open

CI/CD system doesn't resolve environment variables #65

MaxMichel2 opened this issue Jun 27, 2023 · 1 comment

Comments

@MaxMichel2
Copy link

Using this plugin, I am able to easily keep my API keys locally and not upload them via git.

However, when using the Gitlab CI system to deliver application via runners, this plugin doesn't resolve the keys in environment variables defined in Gitlab (ORG_GRADLE_PROJECT_) and defaults to using the default variables in the specified file (local.defaults.properties for example).

The expected behaviour is:

  • Check for the given properties file (local.properties)
  • Check environment variables
  • Use the default properties file (local.defaults.properties)
@fedesenmartin
Copy link

I use bitriss(no idea for gitlab ci) and creating a script that creates and fills local.properties file worked for me

The script:

#!/usr/bin/env bash
cat > "./local.properties" <<- FILE_CONTENT
SECRET_VARIABLE1=value1
SECRET_VARIABLE2=value2
FILE_CONTENT

note that the values should be stored in secrets variables in github/bitrise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants