Command Line Usage

kas - setup tool for bitbake based project

usage: kas [-h] [--version] [-d] [-l {debug,info,warning,error,critical}]
           {build,checkout,dump,for-all-repos,shell,menu} ...

Positional Arguments

cmd

Possible choices: build, checkout, dump, for-all-repos, shell, menu

sub command help

Named Arguments

--version

show program’s version number and exit

-d, --debug

Enable debug logging (deprecated, use –log-level debug).

-l, --log-level

Possible choices: debug, info, warning, error, critical

Set log level (default: info)

Default: 'info'

Environment Variables

kas uses a number of environment variables to configure its behavior. The Variables Glossary provides an overview, wherein the tuple (C,K,E) denotes the scope of the variable.

Variable Scope

kas-container (C)

The variable is processed or forwarded by the kas-container script. For some variables, the variable is re-written to the container’s directory layout.

Note

The env section of the project configuration can be used to make arbitrary environment variables available to the build environment. When invoking the build via kas-container, make sure to also forward the corresponding environment variables into the container.

kas (K)

The variable is processed by kas itself. Some variables (e.g. the credentials for the awscli) are re-written to configuration files to also support older versions of the tooling.

build environment (E)

The variable is exported into the build environment. In this environment, the bitbake command is executed.

Variables Glossary

Environment variables	Description
KAS_WORK_DIR (C, K)	The path of the kas work directory, current work directory is the default.
KAS_BUILD_DIR (C, K)	The path build directory, ${KAS_WORK_DIR}/build is the default.
KAS_REPO_REF_DIR (C, K)	The path to the repository reference directory. Repositories in this directory are used as references when cloning. In order for kas to find those repositories, they have to be named in a specific way. The repo URLs are translated like this: “https://github.com/siemens/meta-iot2000.git” resolves to the name “github.com.siemens.meta-iot2000.git”. Repositories that are not found will be cloned below this directory. Multiple instances of kas can simultaneously work on the same directory, as long as the underlying filesystem is POSIX compatible.
KAS_DISTRO KAS_MACHINE KAS_TARGET KAS_TASK (C, K)	This overwrites the respective setting in the configuration file.
KAS_PREMIRRORS (C, K)	Specifies alternatives for repo URLs. Just like bitbake PREMIRRORS, this variable consists of new-line separated entries. Each entry defines a regular expression to match a URL and, space-separated, its replacement. E.g.: “http://.*.someurl.io/ http://localmirror.net/”
DISTRO_APT_PREMIRRORS (C)	Specifies alternatives for apt URLs. Just like KAS_PREMIRRORS.
KAS_CLONE_DEPTH (C, K)	Perform shallow git clone/fetch using –depth=N specified by this variable. This is useful in case CI always starts with empty work directory and this directory is always discarded after the CI run.
SSH_PRIVATE_KEY (K)	Variable containing the private key that should be added to an internal ssh-agent. This key cannot be password protected. This setting is useful for CI build servers. On desktop machines, an ssh-agent running outside the kas environment is more useful.
SSH_PRIVATE_KEY_FILE (K)	Path to the private key file that should be added to an internal ssh-agent. This key cannot be password protected. This setting is useful for CI build servers. On desktop machines, an ssh-agent running outside the kas environment is more useful.
SSH_AUTH_SOCK (C,K,E)	SSH authentication socket. Used for cloning over SSH (alternative to SSH_PRIVATE_KEY or SSH_PRIVATE_KEY_FILE).
DL_DIR SSTATE_DIR SSTATE_MIRRORS (C,K,E)	Environment variables that are transferred to the bitbake environment.
TMPDIR (K,E)	Directory for temporary files.
http_proxy https_proxy ftp_proxy no_proxy (C,K,E)	These variables define the proxy configuration bitbake should use.
GIT_PROXY_COMMAND (E) NO_PROXY (C,K,E)	Set proxy for native git fetches. NO_PROXY is evaluated by OpenEmbedded’s oe-git-proxy script.
SHELL (C,K,E)	The shell to start when using the shell plugin.
TERM (C,K,E)	The terminal options used in the shell plugin.
AWS_CONFIG_FILE AWS_ROLE_ARN AWS_SHARED_CREDENTIALS_FILE AWS_WEB_IDENTITY_TOKEN_FILE (K,C)	Path to the awscli configuration and credentials files that are copied to the kas home dir.
GIT_CREDENTIAL_HELPER GIT_CREDENTIAL_USEHTTPPATH (K,C)	Allows one to set and configure the git credential helper in the .gitconfig of the kas user.
GITCONFIG_FILE (K,C)	Path to a .gitconfig file which will be copied to the kas home dir as .gitconfig.
NETRC_FILE (K,C)	Path to a .netrc file which will be copied to the kas home dir as .netrc.
REGISTRY_AUTH_FILE (K,C)	Path to a container registry authentication file.
CI_SERVER_HOST CI_SERVER_PORT CI_SERVER_PROTOCOL CI_SERVER_SHELL_SSH_HOST CI_SERVER_SHELL_SSH_PORT CI_JOB_TOKEN CI_JOB_URL CI_REGISTRY CI_REGISTRY_USER (K)	Environment variables from GitLab CI, if set .netrc is configured to allow fetching from the GitLab instance. An entry will be appended in case NETRC_FILE was given as well. Note that if the file already contains an entry for that host most tools would probably take that first one. The job url is added to the provenance attestation (if enabled). If CI_REGISTRY and CI_REGISTRY_USER is also set, a container registry login file is created, which is used by docker, podman and skopeo. In case REGISTRY_AUTH_FILE was given as well, the CI login data will be appended to that file. The required base64 encoded login data is generated by kas.
GITHUB_ACTIONS GITLAB_CI (K)	Environment variables from GitHub actions or GitLab CI. If set to true, .gitconfig is automatically imported. For details, see GITCONFIG_FILE.
REMOTE_CONTAINERS (K) REMOTE_CONTAINERS_<x> (K,E)	Environment variables related to VSCode Remote Containers. If running in this environment, .gitconfig is automatically imported.
BB_NUMBER_THREADS PARALLEL_MAKE (C,K,E)	Environment variables to control the concurrency.

For details about the access of remote resources, see Credential Handling.