I want to set the max-time as a variable instead of hard coding it.
But I can't use this. I will get this error. Anyway around it?
There is an error in your bitbucket-pipelines.yml at [options > max-time]. To be precise: This value should be an integer (it is currently defined as a string).
Most likely not the answer you're looking for: As YAML has no support for environment variables (there is no such thing like environment in context of the YAML file format), instead of a variable (that does not exists) use an invariant, e.g. write in the number verbatim.
Alternatively if there is a step that breaks your dynamic maximum execution time, use some more or less standard tooling to limit how long a command within the step-script is allowed to run (e.g. by using the `timelimit` utility or similar).
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events