Verified Commit e6926477 authored by Matthew Kenigsberg's avatar Matthew Kenigsberg
Browse files

Move some links to end of file

parent 222bfda8
......@@ -5,11 +5,10 @@ author: Michael Hofmann
---
The CKI pipeline is powered by the internal PSI OpenShift cluster running on
[x86\_64 machines](../news/2018-11-08-hello-world.md). For compiling
kernels on `x86_64`, the native compiler toolchain is used. For all other
architectures, the kernel is cross-compiled. While this setup is supported by
the RHEL cross-compiler team for the kernel itself, this is not the case for
the kernel tools.
[x86\_64 machines]. For compiling kernels on `x86_64`, the native compiler
toolchain is used. For all other architectures, the kernel is cross-compiled.
While this setup is supported by the RHEL cross-compiler team for the kernel
itself, this is not the case for the kernel tools.
Up to now, this was not a problem as the CKI pipeline did not build those RPMs.
As that is going to change in the near future, we would like to build native
......@@ -64,6 +63,7 @@ for `FROM`) to buildah is enough to to build `arm64` images instead of native on
The code in this post can be found in the [container images] repository.
[x86\_64 machines]: ../news/2018-11-08-hello-world.md
[container images]: https://gitlab.com/cki-project/containers/
[builder container]: https://gitlab.com/cki-project/containers/-/blob/main/builds/buildah.in
[qemu-user-static]: https://github.com/multiarch/qemu-user-static
......
......@@ -4,9 +4,9 @@ date: "2020-09-08"
author: Michael Hofmann
---
In the [last post](2020-09-07-building-foreign-arch-images.md), we
succeeded in building foreign arch images via qemu. As each architecture gets
its own tag, it becomes a bit cumbersome to use them across architectures.
In the [last post], we succeeded in building foreign arch images via qemu. As
each architecture gets its own tag, it becomes a bit cumbersome to use them
across architectures.
Luckily, buildah supports multi-arch manifests which allow the client to choose
the suitable image for the current architecture by itself. Again, the
......@@ -85,5 +85,6 @@ flawlessly on the runners on gitlab.com for all registries.
The code in this post can be found in the [container images] repository.
[last post]: 2020-09-07-building-foreign-arch-images.md
[DevConf.CZ 2020 presentation]: https://www.youtube.com/watch?v=SYJgkkjqd7s
[container images]: https://gitlab.com/cki-project/containers/
......@@ -11,9 +11,8 @@ mr: 1
## Abstract
This document serves as a template for new Request for Comment (RFC) documents.
The process behind them is described in
[CKI-001](cki-001-cki-feedback-mechanism.md). This abstract should contain a
one paragraph explanation of the RFC.
The process behind them is described in [CKI-001]. This abstract should contain
a one paragraph explanation of the RFC.
## Motivation
......@@ -36,4 +35,5 @@ Why should we not do this?
Which alternative approaches are available instead of the proposed solution?
Why is the proposed solution substantially better?
[CKI-001]: cki-001-cki-feedback-mechanism.md
<!-- vi: set spell spelllang=en: -->
......@@ -14,8 +14,7 @@ keyword.
## TestCaseNeeded
* See [Contributing Tests](onboarding.md) for
steps to onboard a new testcase to CKI.
* See [Contributing Tests] for steps to onboard a new testcase to CKI.
* If the `TestCaseNeeded` keyword is added, please include the suggested test
steps in a Bugzilla comment. It is possible that an existing test can be
updated to verify this feature or target additional hardware.
......@@ -32,3 +31,5 @@ keyword.
* An existing test case exists, please add a Bugzilla comment with a link if
the test source is public
[Contributing Tests]: onboarding.md
......@@ -120,10 +120,11 @@ kpet run generate \
bkr job-submit job.xml
```
For complete details on how to use kpet and kpet-db, please see the [Readme](https://gitlab.com/cki-project/kpet/-/blob/main/README.md)
For complete details on how to use kpet and kpet-db, please see the [Readme]
[kpet]: https://gitlab.com/cki-project/kpet
[kpet database]: https://gitlab.com/cki-project/kpet-db
[kpet-db/index.yaml]: https://gitlab.com/cki-project/kpet-db/blob/main/index.yaml
[kpet-db sets]: https://gitlab.com/cki-project/kpet-db/blob/main/index.yaml
[kpet-db example]: https://gitlab.com/cki-project/kpet-db/-/tree/main/suites/example
[Readme]: https://gitlab.com/cki-project/kpet/-/blob/main/README.md
......@@ -41,7 +41,7 @@ kpet run generate \
--sets kt1
```
See [KPET - Patch Testing](kpet.md) for more details.
See [KPET - Patch Testing] for more details.
Steps to enable this feature for your scratch builds:
......@@ -64,3 +64,4 @@ to use this option if the build works for you or renaming is involved.
[kpet]: https://gitlab.com/cki-project/kpet
[kpet-db sets]: https://gitlab.com/cki-project/kpet-db/blob/main/index.yaml
[KPET - Patch Testing]: kpet.md
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment