We are getting the message, "A variable value contains an illegal string or character" from Bitbucket Pipeline.
The Environment Variable Document, unless I missed it, doesn't mention any limits on values. It doesn't say anything about escaping characters in the values.
What characters are not valid? Are there any escaping mechanisms?
Hey @Davina Adisusila I'm having exactly the same issue. I do not see any illegal characters on my env vars.
Opening the validator shows this:
I even tried to use the env vars without the double quotes to no avail, still getting this:
I do have, of course, the referenced variables defined in my environment variables page set.
Is this a known issue... something we are doing wrong perhaps?
I love to have the pipelines integrated with the source control but unfortunately storing the credentials on the YAML is not an option as you'd guess.
Thanks in advance!
Just to add to the conversation: using the ENV VARS within the pipelines section works; I added the following as the last command of the pipeline for instance:
echo "Database name is $DB_NAME"
And it does output in the log the database name, so it seems that only when using env vars in the definitions section they are not properly parsed:
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot