I am operating a customized workflow on Xcode Cloud
. The workflow is failing on the Construct
step as a result of it couldn’t discover my .env
file. This sounds logical since I am not pushing my .env
file; it isn’t being tracked by git
even.
I’ve already setup my customized atmosphere variables on the Xcode Cloud
workflow.
I can dynamically create the .env
file in my ci_post_clone.sh
script. Like:
// Like as an illustration on Github Actions, I may learn my repository secrets and techniques like so.
// ${{secrets and techniques.MY_ENV_VAR}}
echo ${{secrets and techniques.MY_ENV_VAR}} >> .env
echo ${{secrets and techniques.MY_SECOND_ENV_VAR}} >> .env
How can I entry Xcode workflow atmosphere variables identical to I am accessing the Github
secrets and techniques? I want an answer to learn these variables from my customized ci_post_clone.sh
script.