You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Default environment variables needs to available in build jobs so users can write scripts upon that predefined variables.
List of variables that needs to be available (I borrowed that from Travis):
ABSTRUSE_BRANCH
for push builds, or builds not triggered by a pull request, this is the name of the branch.
for builds triggered by a pull request this is the name of the branch targeted by the pull request.
for builds triggered by a tag, this is the same as the name of the tag (ABSTRUSE_TAG)
ABSTRUSE_BUILD_DIR
The absolute path to the directory where the repository being built has been copied on the worker.
ABSTRUSE_BUILD_ID
The id of the current build that Abstruse CI uses internally.
ABSTRUSE_JOB_ID
The if of the current job that Abstruse CI uses internally.
ABSTRUSE_COMMIT
The commit that the current build is testing.
ABSTRUSE_EVENT_TYPE
Indicates how the build was triggered. One of push or pull_request
ABSTRUSE_PULL_REQUEST
The pull request number if the current job is a pull request, “false” if it’s not a pull request.
ABSTRUSE_PULL_REQUEST_BRANCH
if the current job is a pull request, the name of the branch from which the PR originated.
if the current job is a push build, this variable is empty ("")
ABSTRUSE_TAG
If the current build is for a git tag, this variable is set to the tag’s name.
ABSTRUSE_PULL_REQUEST_SHA
if the current job is a pull request, the commit SHA of the HEAD commit of the PR.
if the current job is a push build, this variable is empty ("")
ABSTRUSE_SECURE_ENV_VARS
Set to true if there are any encrypted environment variables.
Set to false if no encrypted environment variables are available.
ABSTRUSE_TEST_RESULT
is set to 0 if the build is successful and 1-255 if the build is broken.
this variable is available only since test command is executed
The text was updated successfully, but these errors were encountered:
Default environment variables needs to available in build jobs so users can write scripts upon that predefined variables.
List of variables that needs to be available (I borrowed that from Travis):
ABSTRUSE_BRANCH
ABSTRUSE_TAG
)ABSTRUSE_BUILD_DIR
ABSTRUSE_BUILD_ID
ABSTRUSE_JOB_ID
ABSTRUSE_COMMIT
ABSTRUSE_EVENT_TYPE
push
orpull_request
ABSTRUSE_PULL_REQUEST
ABSTRUSE_PULL_REQUEST_BRANCH
""
)ABSTRUSE_TAG
ABSTRUSE_PULL_REQUEST_SHA
""
)ABSTRUSE_SECURE_ENV_VARS
true
if there are any encrypted environment variables.false
if no encrypted environment variables are available.ABSTRUSE_TEST_RESULT
0
if the build is successful and1-255
if the build is broken.test
command is executedThe text was updated successfully, but these errors were encountered: