Kas siemens github KAS_REPO_PATH: The path of the local directory where this repository is checked out, relative to the directory where kas is executed. Python 2 3 2 1 Updated Setup tool for bitbake based projects. What issues do you see with it? Yeah, kas-container cannot parse the complete kas config hierarchy, thus needs help via --runtime-args "-e var=value". ssh/known_hosts finally see the log message Adding GitLab CI ssh -> https rewrites. yml docker run -v /<worktre I'm new to kas and trying things out. $ docker pull ghcr. /eu-terminal-distro. I was debugging using plain bitbake commands and all was fine, while in CI it always failed to fetch some URL from a private repository and this dr Provided by: kas_4. I tried -E, --preserve-e Setup tool for bitbake based projects. /netrc kas shell my_kas_config. /kas-container build kas-qemu. Use as base image in Dockerfile: FROM ghcr. Info about system: kas 3. After removing bblayers. Loading. 2 (installed by pip) Ubuntu 22. yml. Nice work :) When going to kas shell is there a way to get . Contents: Setup tool for bitbake based projects. I'd like to use this to create one configuration file per OE base This tool provides an easy mechanism to setup bitbake based projects. 92M. Sign in Product siemens; kas MIT License; 391 stars Last published 8 days ago. Reload to refresh your session. zst. Closes: #42 Signed-off-by: Jan Kiszka <jan. Hi, I'm using kas version 4. Xref: Felix Moessbauer <felix. The repo URLs are translated like this: “https://github. 2 and having some issues with do_fetch method of some recipe. yml The QEMU build by default uses the Linux kernel from the Debian repositories. Hi, We want to create a download mirror as part of our kas build procedure. Sign in Product siemens; kas MIT License; 383 stars Last published 2 days ago. MX8M Plus EVK with Siemens KAS build tool, Start with Yocto/Gatesgarth, base on imx-5. I'm still trying to sort what you are writing KAS_SSH_DIR should be equivalent to --ssh-dir irrespective of build vs. You can also validate that (or prove me wrong) by using -d (verbose mode) and comparing the docker command lines. Contribute to siemens/meta-iot2050 development by creating an account on GitHub. yaml always asks for Username Setup tool for bitbake based projects. GitHub is where people build software. 0-1_all NAME kas - kas Documentation INTRODUCTION This tool provides an easy mechanism to setup bitbake based projects. Your private one could be adding --runtime-args '-v <host>:<container>' to your kas-container call. moessbauer@siemens. sample. 10; Repos on gitlab with 2FA activated. SSH_PRIVATE_KEY is not supported with kas-container. br Hey there, I'm super happy with how kas brings a lot more structure to my build system. Kas makes the setup of a Yocto build environment super simple and super fast. You signed in with another tab or window. This is now working for use with google repo with 'repo manifest -r -o release. conf. com> Signed-off-by: Jan Kiszka <jan. Issues 16. Jailhouse demonstration and testing images. Notifications You must be signed in to change notification settings; Fork 152; Star 382. com> ISAR Layer for Coral TPU. For example, I have custom l Thanks for the speedy reply, Jan. Contribute to siemens/jailhouse-images development by creating an account on GitHub. I was wonderi Isar layer to support RISC-V architecture for QEMU and also for upcoming NOEL-V hardware within SELENE EU project - isar-riscv/kas-container at main · siemens/isar-riscv Hey, the order of layers in BBLAYERS in the generated build directory deviates from the order in my yml configuration. Access tokens are generated and added to a netrc. But nobody would be missing repo if this use case would work with KAS. Hi, does the fetch work if running it without kas? Before using the credential helper, did you try the following: running an ssh agent (auto-forwarded into kas, when SSH_AUTH_SOCK is set, for kas-container, use --ssh-agent); using password-less ssh keys (auto-forwarded into kas, for kas-container use --ssh-dir ~/. 3. SSTATE_MIRRORS would then have to point As the title says, somehow kas does not pick up the netrc. SIMATIC IOT2050 Isar/Debian Board Support Package Python 131 siemens/. You can quickly see that from scanning the script - no special handling. That way a layer maintainer would maintain the kas. ssh); Further, please also check if git rewrites (insteadof) are needed. kiszka@siemens. sample local. Neither of the two options look decent to me as of right now. Setup tool for bitbake based projects. ssh build kas/project-latest. kas kas Public. kas build <yml file> --runonly=fet Hi, It seems that kas has hardcoded build as default name for the build directory inside working directory. the repository for NXP i. only *. yml --command "echo it works. A separate plugin so it can be invoked once in a multi Setup tool for bitbake based projects. git” resolves to the Welcome to the kas documentation, a setup tool for bitbake based projects See https://github. KAS_REPO_NAME: The name of the current repository determined by either the name property or by the key used for this repo in the config file. You switched accounts on another tab or window. SIMATIC IOT2000 Yocto Board Support Package. See https://github. One could add a kas. com/orgs/siemens/packages/container/kas%2Fkas-isar/versions for all available Welcome to the kas documentation, a setup tool for bitbake based projects¶. siginfo are in cache. 10. 2. Instead kas is using a project configuration file Setup tool for bitbake based projects. xml'. Containers add a whole stack of new dependencies and introduce various other issues. I update things, run kas build, if everything works fine I update the kas configuration with that latest commit. If I dont create . github’s past year of commit activity. If you'd like to opt out, please create your own Code of Conduct. This is BBLAYERS: BBLAYE Setup tool for bitbake based projects. io/ siemens / kas/kas-isar:2. Hello. Contribute to siemens/meta-coral development by creating an account on GitHub. com/orgs/siemens/packages/container/kas%2Fkas/versions and https://github. 4) ISO auditor comes and believes everything is under control to rebuild this exact image in a galaxy far far away. siemens / kas Public. 6. Ok, this is also stated in the documentation, but maybe we should stress it a bit more: There must be no SSH configuration. Yet, build still take too much time to complete, everything is being rebuilt, and no archive file of type . gz (25 kB) ERROR: Command errored out with exit status 1: command: /usr/bin/python3 -c Setup tool for bitbake based projects. It needs to know this value but has no parser for configs with all their includes and overrides (except for very Dear project maintainers, The default Siemens Code of Conduct will be applied to this repository on October 7, 2024. You signed out in another tab or window. KAS_BUILD_DIR is not really a project setting, it's a local decision. sample where a layer would keep its example written in kas lingo. shell. " by keeping the command argument separate and injecting it via appropriate quoting into the argument array. Contributors 61 + 46 contributors Open an issue. Hello, I am unable to install kas using pip. I'd like to restart the discussion as in my use case simply passing the variables to bitbake via env and BB_ENV_EXTRAWHITE is not enough. Total downloads 3. 3) And CI put's a git tag on that file. Kas starts a Docker container, clones the layer In order for kas to find those repositories, they have to be named in a spe-cific way. About. Cache variables such as SSTATE_DIR and DL_DIR has been set up respectively to /sstate-cache and /downloads. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects. Usually, this is explained in a README. pip install kas results in the following error: » pip install kas Collecting kas Using cached kas-2. For more details, see the pull request in our organization repo. com/siemens/meta-iot2000. SIMATIC IOT2050 Isar/Debian Board Support Package. The ideal way would be to have KAS check out the git repo with common kas files and still be able to reference them from the command line. Yet another special dance needed to preserve argument boundaries while moving them around: This trick enables kas-container shell kas. 94M. Hey, I usually now work within our proprietary meta layer within the downloaded kas sources. If you need to use the same kernel as in the NOEL-V build, please include a second . com> fmoessbauer added a commit to fmoessbauer/kas that referenced this issue Sep 30, 2024. It is quite problematic if we want to build multiple images from the same set of layer repositories. 25% of the code is the URL-to-name logic so this really should be part of kas IMHO. git clone manually (not via kas) works fine. On top we could have kas to-bitbake kas. If I only checkout the layer (using kas), navigate to it and then run git lfs pull on it, I get the archives and I can proceed as usual. zst exists in cache. Contribute to siemens/kas development by creating an account on GitHub. We generally recommend CI parametrization via env vars, though. com/orgs/siemens/packages/container/kas%2Fkas-isar/versions for all available Setup tool for bitbake based projects. This should also enable the use of kas in the github codespaces (not tested). Navigation Menu Toggle navigation. Automatically cloning/fetching the repositories if KAS_REPO_REF_DIR is set seems like a good idea, but I can see an argument that the reference directory might be a shared resource so racing to do the fetches would be bad. When I checkout a KAS/Yocto based GIT repo branch into a working folder using the GIT worktree feature, the build fails at an early stage: $ kas/kas-container -v --ssh-dir ${HOME}/. The downloading of sources and then configuration has to be done by hand. tar. Skip to content. Code; Issues 14; Pull requests 2; Actions; Security; You signed in with another tab or window. Setup tool for bitbake based projects Python 400 159 meta-iot2050 meta-iot2050 Public. xml Setup tool for bitbake based projects. If you have any further questions feel free to comment in the PR or reach out via email. Saved searches Use saved searches to filter your results more quickly Setup tool for bitbake based projects. I'm trying to do a simple CI/CD that runs kas docker image and builds my image (which depends on private repositories) This is what I've tried: variables: GIT_SUBMODULE_STRATEGY: recursive before_script: - git config --global cred Problem is that we would have to parse and translate the elements SSTATE_MIRRORS so that we have local path from host POV and can create mount option for the container runtime. bashrc sourced? My usecase is that I define a bunch of aliases I'd like to be able to use when working on recipes. yml file as shown below. But the documentation says that's prohibited. We call kas with a project configuration file: kas-container build . sample and have Setup tool for bitbake based projects. 9-1. However, I'm stuck now at about 60% build progress with the following exception which I do not get when not using my kas configuration. 0. If I use bitbake shell and try to git lfs pull in that layer I GitHub is where people build software. In my case I would really like to reference the variables in env (or even all of the environment kas was started in) in the configuration files. So we want to send --runonly=fetchbitbake argument as part of our kas build procedure. That would be a generic solution. To enhance that workflow I was wondering if a refspec=${AUTOREV} given that a branch (or if not fallback to master) is provided wouldn't be an option. . Nevertheless, kas is going to clone my repos using ssh. Or why should all users of your configs split the build dirs like you suggest? But even if we wanted to introduce a configurable default value to the config, that would not work across kas-container. Contribute to siemens/meta-iot2000 development by creating an account on GitHub. KAS_REPO_URL: The URL from which this repository was cloned, or an empty string if no When I use kas to checkout/build that layer my LFS pointers are not replaced by the actual files. . My current work-around is to share them with a Setup tool for bitbake based projects. The OpenEmbedded tooling support starts at step 2 with bitbake. conf (just to see that I'm not mistaken) I run kas build mconfig. add support for Setup tool for bitbake based projects. Command: NETRC_FILE=. hfdho gqfyouk xswgmc vytn eyujxqv tibvebt gscjr lyuly ibz xjcfxouz