6b65de3e2f
By default git only fetches references under the refs/heads/ tree, this patch adds support to kas to enable you to specify references outside of the ref/heads tree. This is useful as it allows you to use uncommitted gerrit patchsets, Gitlab merge requests or github pull requests that live under refs/changes/, refs/merge-requests and refs/pull as the reference for a repo allowing the use of in development changes. When a refsepc is defined that starts with refs/ an additional git fetch operation is preformed on the repo to explicitly fetch the reference given so it can be checked out for use. Signed-off-by: Drew Reed <drew.reed@arm.com> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
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.