SiegfriedSiegert/PTU5KAS
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e274886ab0
PTU5KAS/README.rst

43 lines
1.6 KiB
ReStructuredText
Raw Normal View History

Initial public release This is the first public release of kas. Signed-off-by: Daniel Wagner <daniel.wagner@siemens.com>
2017-06-14 13:36:37 +02:00
Setup tool for bitbake based projects
=====================================
Switch to github workflow Add the github/ghcr equivalent to travis/dockerhub. With this in place, we can also deploy the next and latest images to ghcr. Adjust Dockerfile.isar accordingly. Also update the badge shown in the README. We model the workflow with github a bit differently than so far: next and master branch are different workflows. The former includes testing, the latter just updates the container image. This is based on the (offline) workflow to push changes to next first and have no commits in master that haven't been in next before, except for release commits. The master workflow also triggers on tags in which case it additionally tags the container images accordingly and pushed that as well. Travis is removed in the same run to avoid pushing differently built images to the different registries. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2020-09-23 11:36:12 +02:00
+--------------------+
| Build Status |
+====================+
| |workflow-master|_ |
+--------------------+
| |workflow-next|_ |
+--------------------+
ci: Add Travis build status batches to README The batches also provide a link to the build status on travis-ci.org Signed-off-by: Daniel Mohr <daniel.mohr@evosoft.com>
2017-06-21 15:50:24 +02:00
Switch to github workflow Add the github/ghcr equivalent to travis/dockerhub. With this in place, we can also deploy the next and latest images to ghcr. Adjust Dockerfile.isar accordingly. Also update the badge shown in the README. We model the workflow with github a bit differently than so far: next and master branch are different workflows. The former includes testing, the latter just updates the container image. This is based on the (offline) workflow to push changes to next first and have no commits in master that haven't been in next before, except for release commits. The master workflow also triggers on tags in which case it additionally tags the container images accordingly and pushed that as well. Travis is removed in the same run to avoid pushing differently built images to the different registries. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2020-09-23 11:36:12 +02:00
.. |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
ci: Add Travis build status batches to README The batches also provide a link to the build status on travis-ci.org Signed-off-by: Daniel Mohr <daniel.mohr@evosoft.com>
2017-06-21 15:50:24 +02:00
Initial public release This is the first public release of kas. Signed-off-by: Daniel Wagner <daniel.wagner@siemens.com>
2017-06-14 13:36:37 +02:00
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.
Massage README * reorder to have most relevant information first * adjust docker description * improve consistency of examples * add community resources Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-06-18 09:55:12 +02:00
Key features provided by the build tool:
README: Convert to structured text This is a preferred format of Python READMEs and also properly rendered by github. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-07-17 22:38:02 +02:00
Massage README * reorder to have most relevant information first * adjust docker description * improve consistency of examples * add community resources Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-06-18 09:55:12 +02:00
- clone and checkout bitbake layers
- create default bitbake settings (machine, arch, ...)
- launch minimal build environment, reducing risk of host contamination
- initiate bitbake build process
Initial public release This is the first public release of kas. Signed-off-by: Daniel Wagner <daniel.wagner@siemens.com>
2017-06-14 13:36:37 +02:00
README: Convert to structured text This is a preferred format of Python READMEs and also properly rendered by github. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-07-17 22:38:02 +02:00
See the `kas documentation <https://kas.readthedocs.io>`_ for further details.
README: Leave notice on inherit integrity weaknesses of repo fetches Neither git nor hg currently provide a production-ready replacement for weak SHA-1 commit IDs. Furthermore, kas mixes commit IDs and symbolic commit names in refspec. This permits attackers who gained control over a repository that kas fetches from to present manipulated content without kas noticing this. Aditya Sirish A Yelgundhalli recently reported one potential attack scenario, using branches that shadow commit IDs. While trying to mitigate this particular case, it became clear that there is no simple solutions with the given tools and interfaces. For now, warn prominently that only trusted sources should be used. There are extensions planned to address the issue at its root, likely by introducing content checksums. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2023-02-12 18:43:42 +01:00
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.
Reference in New Issue Copy Permalink