420bf399b3
If a remote branch is referenced as refs/heads/<branch>, also drop the heads/ from the local branch name to have a consistent naming. This wasn't noticed so far because the primary use case of refs/ is addressing symbolic refs in upstream, and the related test case (test_refspec_absolute) was papering over another hidden kas issues while using refs/heads/. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> |
||
---|---|---|
.github | ||
contrib | ||
docs | ||
image-tests | ||
kas | ||
scripts | ||
tests | ||
.coveragerc | ||
.dockerignore | ||
.flake8 | ||
.gitignore | ||
.readthedocs.yaml | ||
CHANGELOG.md | ||
container-entrypoint | ||
CONTRIBUTING.md | ||
Dockerfile | ||
kas-container | ||
kas-docker | ||
LICENSE | ||
pyproject.toml | ||
README.rst | ||
run-kas | ||
SECURITY.md | ||
setup.py |
Setup tool for bitbake based projects ===================================== +--------------------+ | Build Status | +====================+ | |workflow-master|_ | +--------------------+ | |workflow-next|_ | +--------------------+ .. |workflow-master| image:: https://github.com/siemens/kas/workflows/master/badge.svg .. _workflow-master: https://github.com/siemens/kas/actions?query=workflow%3Amaster .. |workflow-next| image:: https://github.com/siemens/kas/workflows/next/badge.svg .. _workflow-next: https://github.com/siemens/kas/actions?query=workflow%3Anext This tool provides an easy mechanism to setup bitbake based projects. The OpenEmbedded tooling support starts at step 2 with bitbake. The downloading of sources and then configuration has to be done by hand. Usually, this is explained in a README. Instead kas is using a project configuration file and does the download and configuration phase. Key features provided by the build tool: - clone and checkout bitbake layers - create default bitbake settings (machine, arch, ...) - launch minimal build environment, reducing risk of host contamination - initiate bitbake build process See the `kas documentation <https://kas.readthedocs.io>`_ for further details. SECURITY NOTICE --------------- At this stage, kas does not validate the integrity of fetched repositories. Make sure to only pull from trusted sources to ensure that the selected revisions are the expected ones, specifically when using mirrors. Later versions of kas may introduce integrity validation mechanisms such as cryptographic checksums to strengthen supply chain security.