$GIT_SSL_CAINFO =" C:\GitLab-Runner\builds\0\project-1.tmp\GIT_SSL_CAINFO " $GIT_SSL_CAINFO | Out-File " C:\GitLab-Runner\builds\0\project-1.tmp\GIT_SSL_CAINFO " New-Item -ItemType directory -Force -Path " C:\GitLab-Runner\builds\0\project-1.tmp " | out-null $ env : GITLAB_CI = $GITLAB_CI $GIT_SSL_CAINFO ="" $ env : CI_SERVER_REVISION = $CI_SERVER_REVISION $GITLAB_CI =" true " $ env : CI_SERVER_VERSION = $CI_SERVER_VERSION $CI_SERVER_REVISION ="" $ env : CI_SERVER_NAME = $CI_SERVER_NAME $CI_SERVER_VERSION =""
$ env : CI_SERVER = $CI_SERVER $CI_SERVER_NAME =" GitLab CI " $ env : CI_PROJECT_DIR = $CI_PROJECT_DIR $CI_SERVER =" yes " $ env : CI_PROJECT_ID = $CI_PROJECT_ID $CI_PROJECT_DIR =" Z:\Gitlab\tests\test\builds\0\project-1 " $ env : CI_REPOSITORY_URL = $CI_REPOSITORY_URL $CI_PROJECT_ID =" 1 " $ env : CI_JOB_ID = $CI_JOB_ID $CI_REPOSITORY_URL =" Z:\Gitlab\tests\test " $ env : CI_COMMIT_REF_NAME = $CI_COMMIT_REF_NAME $CI_JOB_ID =" 1 " $ env : CI_COMMIT_BEFORE_SHA = $CI_COMMIT_BEFORE_SHA $CI_COMMIT_REF_NAME =" main " $Error ActionPreference = "Continue" # This will be set to 'Stop' when targetting PowerShell Core echo "Running on $( :: MachineName ). Passing the filename to the following command: The generated PowerShell script is executed by saving its content to a file and PowerShell doesn’t support executing the build in context of another user. In 14.0 and later, the default is PowerShell Core Edition.
PowerShell Desktop Edition is the default shell when a new runner is registered on Windows using GitLab Runnerġ2.0-13.12.
Learn how to gain access to the CMD shell when PowerShell is the default shell. All commands are executed in Batch context. In GitLab Runner 14.0 and later, this is the default when registering a new runner. All commands are executed in PowerShell Core context. In GitLab Runner 12.0-13.12, this is the default when registering a new runner.
All commands are executed in PowerShell Desktop context. All commands executed in Sh context (fallback for bash for all Unix systems) All commands executed in Bash context (default for all Unix systems) The build steps are receivedįrom the commands defined in the script directive in. The shells don’t have any configuration options.