I’m attempting to verify that the following use case is not possible (and request that it be added it if not )
I wish to do something like:
$ drone exec -e ENV_VAR=value --local
ENV_VAR be set as an environment variable across all build steps in a
My use case:
Certain environment variables are only available on our Drone server. These variables are integral to running the build successfully. For example, this is how we store service account credentials to various other systems. Without said env vars, the build will always fail, leaving us to to repeatedly push (or force push) new commits just to debug what’s wrong with our
So my questions:
- Is this not possible? I’ve looked around but fear I may have missed something.
- Is there a better (currently functioning) way to get what I’m after?
- (if no to both ) Could this be integrated into a future release?