According to the description of ci-env command, werf should define a set of WERF_* variables and perform some actions to integrate with the CI/CD system.
werf uses the following values for werf environment variables:
WERF_REPO
The value of WERF_REPO is derived from the GITHUB_REPOSITORY GitHub Actions variable (converted to lowercase) and project name from werf.yaml: ghcr.io/$GITHUB_REPOSITORY/<project-name>.
WERF_ADD_ANNOTATION_PROJECT_GIT
The value of WERF_ADD_ANNOTATION_PROJECT_GIT is based on the GITHUB_REPOSITORY GitHub Actions environment variable and composed as follows:
project.werf.io/git=https://github.com/$GITHUB_REPOSITORY
WERF_ADD_ANNOTATION_CI_COMMIT
The value of WERF_ADD_ANNOTATION_CI_COMMIT is extracted from the GITHUB_SHA GitHub Actions environment variable and composed as follows:
ci.werf.io/commit=$GITHUB_SHA
WERF_ADD_ANNOTATION_GITHUB_ACTIONS_RUN_URL
The value of WERF_ADD_ANNOTATION_GITHUB_ACTIONS_RUN_URL is derived from the GITHUB_RUN_ID GitHub Actions environment variable and composed in the following way:
github.ci.werf.io/workflow-run-url=https://github.com/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID
Other variables
Other variables are configured in the regular way described in the overview article:
DOCKER_CONFIG;WERF_LOG_COLOR_MODE;WERF_LOG_PROJECT_DIR;WERF_ENABLE_PROCESS_EXTERMINATOR;WERF_LOG_TERMINAL_WIDTH.
How to use
You can turn on the integration with GitHub Actions by invoking the werf ci-env command with the required positional argument:
werf ci-env github