Rename CIRCLECI variables, with backwards compatibity #20
Conversation
In case the script is used outside of CircleCI.
| : "${SHA1:=$CIRCLE_SHA1}" | ||
| : "${PROJECT_USERNAME:=$CIRCLE_PROJECT_USERNAME}" | ||
| : "${PROJECT_REPONAME:=$CIRCLE_PROJECT_REPONAME}" |
There was a problem hiding this comment.
pls enlightne me. What does the preeceeding colon do here?
There was a problem hiding this comment.
Source ( grep for The following table )
There was a problem hiding this comment.
"these are not the colons you are (i am) looking for"
I meant the initial colon at the start of the line. I find this https://stackoverflow.com/a/4892546
A useful application for
:is if you're only interested in using parameter expansions for their side-effects rather than actually passing their result to a command.In that case, you use the parameter expansion as an argument to either
:orfalsedepending upon whether you want an exit status of 0 or 1. An example might be
: "${var:=$1}"
There was a problem hiding this comment.
Ah sorry I misunderstood - yes, this is correct. If you don't add the : it will try to "run" the result.
There was a problem hiding this comment.
Man, I copypasted from SO
There was a problem hiding this comment.
In case the script is used outside of CircleCI.