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
Environment variables |
Description |
---|---|
|
The path of the kas work directory, current work directory is the default. |
|
The path build directory,
|
|
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. |
|
This overwrites the respective setting in the configuration file. |
|
Specifies alternatives for repo URLs. Just like
bitbake |
|
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. |
|
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 authentication socket. Used for cloning over
SSH (alternative to |
|
Environment variables that are transferred to the bitbake environment. |
|
These variables define the proxy configuration bitbake should use. |
|
Set proxy for native git fetches. |
|
The shell to start when using the shell plugin. |
|
The terminal options used in the shell plugin. |
|
Path to the awscli configuration and credentials files that are copied to the kas home dir. |
|
Allows to set and configure the git credential helper in the .gitconfig of the kas user. |
|
Path to a .gitconfig file which will be copied to the kas home dir as .gitconfig. |
|
Path to a .netrc file which will be copied to the kas home dir as .netrc. |
|
Environment variables from gitlab CI, if set
.netrc is configured to allow fetching from
the gitlab instance. An entry will be appended
in case |
|
Environment variables from github actions. If
set to true, .gitconfig is automatically
imported. For details, see |
|
Environment variables to control the concurrency |
For details about the access of remote resources, see Credential Handling.