Add Semaphore 2.0 Support #473
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds support for [Semaphore’s internal ENV vars](http://ttps://docs.semaphoreci.com/ci-cd-environment/environment-variables/) used for specifying the current git branch and git sha. To note: In the instance of a PR, the `SEMAPHORE_GIT_PR_BRANCH` variable has the expected branch name, whereas if code is being run against a branch directly (ie: `main`), `SEMAPHORE_GIT_BRANCH` is where it can be found. Given how the `findVar` code works - `SEMAPHORE_GIT_BRANCH` will function as a fallback for `SEMAPHORE_GIT_PR_BRANCH`.
|
|
f-moya
approved these changes
Aug 10, 2021
|
@thewatts released ! 👏🏼 |
|
Thank you!!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for Semaphore’s internal ENV vars used for specifying the current git branch and git sha.
To note: In the instance of a PR, the
SEMAPHORE_GIT_PR_BRANCHvariable has the expected branch name, whereas if code is being run against a branch directly (ie:main),SEMAPHORE_GIT_BRANCHis where it can be found.Given how the
findVarcode works -SEMAPHORE_GIT_BRANCHwill function as a fallback forSEMAPHORE_GIT_PR_BRANCH.