KAS-BUILD(1)

πŸ“¦
version 5.4 Β· 3 versions
, in ubuntu stonking

πŸ’… KAS-BUILD β€” the kas build plugin, aka the moment ✨

okay so bestie, say hi to kas-build, the kas build plugin. it's in the kas manual, section 1 (general commands), and it is iconic. this is where you tell kas to go get the repos and then hand the whole thing to bitbake. let's get into it 🫢


🌸 SYNOPSIS 🌸

kas build [-h] [--skip STEP] [--force-checkout] [--update] [-k]
          [--target TARGET] [-c TASK] [--provenance {true,mode=min,mode=max}]
          [config] [extra_bitbake_args ...]

πŸ¦‹ DESCRIPTION πŸ¦‹

Checks out all necessary repositories and builds using bitbake as specified in the configuration file. no cap, that's the whole assignment.

This plugin implements the kas build command. πŸ’–

When this command is executed, kas will checkout repositories, setup the build environment and then invoke bitbake to build the targets selected in the chosen config file. it's giving choreography honestly β€” everyone hits their mark and then bitbake does the actual performance.

When running with --provenance <true|mode=...> kas will generate an provenance attestation for the build. The attestation will be stored in attestation/kas-build.provenance.json in the build directory. For details about provenance, see the build attestation chapter. receipts? we got receipts. 🧾✨

Note: In provenance mode, the command returns with a non-zero exit code in case no artifact is found for at least one entry. so like… if even one entry comes up empty, the vibe check fails and you get a non-zero exit code. not dramatic, just true. πŸ’€

✨ OPTIONS ✨

πŸ‘‘ Positional Arguments

  • config β€” Config file(s), separated by colon. Using .config.yaml in KAS_WORK_DIR if none is specified. yes bestie, it defaults for you, she's thoughtful like that πŸŽ€
  • extra_bitbake_args β€” Extra arguments to pass to bitbake (typically requires separation via --). so you go -- and then just say whatever you need to say to bitbake. she's all ears πŸ“£

πŸ’… Named Arguments

  • --skip=[] β€” Skip build steps. To skip more than one step, use this argument multiple times. the possible choices are: setup_dir, setup_home, make_non_interactive, init_setup_repos, repo_setup_loop, finish_setup_repos, repos_checkout, repos_apply_patches, setup_environ, write_bbconfig. one per use, so stack them like charms on a bracelet πŸ“
  • --force-checkout=False β€” Always checkout the desired commit/branch/tag of each repository, discarding any local changes. discarding any local changes β€” she said what she said, and your local edits are NOT surviving this. 😭
  • --update=False β€” Pull new upstream changes to the desired branch even if it is already checked out locally. even if it's already sitting right there, she's still going to go grab the fresh stuff 🌈
  • -k, --keep-config-unchanged β€” Skip steps that change the configuration. protect the config at all costs 🫢
  • --target β€” Select target to build. point at it. build it. main character target energy πŸ‘‘
  • -c, --cmd, --task β€” Select which task should be executed. three names, one job, we love a flexible queen ✨
  • --provenance β€” Enable provenance attestation generation. the possible choices are: true, mode=min, mode=max. this is the one that drops that attestation/kas-build.provenance.json file we talked about, so like, remember the exit code thing up top fr fr πŸ’œ

🌈 SEE ALSO 🌈

🌸 KAS 🌸

Part of the kas(1) suite. family reunion, everyone's there πŸ₯°


πŸ’– Author πŸ’–

Daniel Wagner, Jan Kiszka, Claudius Heine β€” the founders fr fr, absolute legends, we stan πŸ’œ

Siemens and contributors, 2017-2025


and that's the page bestie! ✨ this was kas version 5.4, dated Jun 25, 2026, for the kas-build(1) manual page. go build something gorgeous, you got this πŸ¦‹πŸ’…πŸ’–

πŸ“¦ where this page comes from