env-vars not available in v1.39.0 #2100
antonneubauer
started this conversation in
General
Replies: 1 comment 1 reply
-
Hey @antonneubauer thank for reaching out! Which type of environment variable exactly are not available? https://maestro.mobile.dev/api-reference/configuration/workspace-configuration Mentioned here? Or the one exported in shell? If you could create a GitHub issue that can help reproducing problem locally. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
TLDR: The following fails with 1.39.0, passes with 1.38.1. The command is part of a job executed on a gitlab runner using docker executor. The tests fail because env vars are not read properly even though they are available in the job environment.
Command:
Since the release of 1.39.0 my flows don't pass anymore because values that were read from environment variables are not available in flows anymore.
They are set and available in the pipeline job (echo-ing them right before maestro execution results in the expected behaviour). The vars contain text that is entered in the flows and looking at the maestro log "null" is entered instead.
I am fairly certain the problem arose with the new release because another pipeline job, with identical setup, runs in parallel using Maestro v1.38.1 and works perfectly fine. When moving the failing job back to v1.38.1 it passes again.
Is anyone else experiencing this? For now I have just fixed the version number but in general I am interested in staying up to date on maestro versions.
Beta Was this translation helpful? Give feedback.
All reactions