-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: rename CI tags #984
feat: rename CI tags #984
Conversation
} | ||
case Bamboo: | ||
return CI{ | ||
Provider: provider, | ||
OriginURL: os.Getenv("bamboo_buildResultsUrl"), | ||
Repo: os.Getenv("bamboo_planRepository_repositoryUrl"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Terminologies: In Bamboo CI, a plan
organizes a series of jobs and their associated configurations. position
is the index of a repository in the plan's configuration. The default position is 0
.
The variable bamboo_planRepository_repositoryUrl
is now replaced with bamboo_planRepository_<position>_repositoryUrl
. There’s no way to dynamically retrieve position
.
For commit SHA information, the only available variable is bamboo_planRepository_<position>_revision
, which also depends on <position>
. The value cannot be accurately determined.
Based on these, I removed the repo url and revision.
Reference: https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html
Note: How can these variables be accessed as environment variables?
Bamboo variables are exported as bash shell variables. All full stops (periods) are converted to underscores. For example, the variable bamboo.my.variable is $bamboo_my_variable in bash. This is related to File Script and Inline Script tasks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description
Rename CI tags.