Skip to content
Snippets Groups Projects
Commit ed963a50 authored by GitBot's avatar GitBot
Browse files

Integrate meta-seconorth-distro/rtc_overlays

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@82258da2

Integrate gitlab-ci/add-test-reporting-to-test-jobs

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@52bae4a1

Lava Testreporting: Add script to generate markdown report for given jobids

Adds scripts for mark down generation.
Adds scripts for lava test result queries.
Adds script to generate a mark down report from this data
Call script from submit_test to generate a report directly
after the testrun.

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@ed67ad82

Integrate gitlab-ci/run-test-from-gitlab-directly

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ab09db0b

CI: Lava Test: Allow to install test image directly from gitlab

The images from the build job can be directly installed from gitlab.
To achive this some changes in the complete pipeline have been needed.

1. The variables used in the build job, like CI_PARAM_IMAGE, ... and
   related variables like BUILDPATH are only valid in the build job now.
2. The build job writes every variable needed in a follow up job into
   build.env. This also includes the url to the fng-install.sh of the
   final image.
3. The build.env file is used as dotenv artifact, as well as normal
   file artifact.
   The dotenv make the written variables automatically available in
   follow up jobs, that are using the aritfacts, like the deploy job.
   The normal file artifact is available via artifact download.
   (I did't found a way to download the dotenv file instead)
4. Some scripts have been added:
   - Find a job inside the pipeline by name, as the id is not known in
     advance.
   - Download all artifacts or one file of the artifacts from a given
     job
   - Download one file of the latest job by name
5. The scripts are used to download the build.env into the test job
   (where not artifacts are needed anymore)
6. The script is sourced and all variables are available inside the
   script.

Additionally this adds a fake build job to the ci-test pipeline, that
copies an image from srv73 and stores it as artifact in a way that a
test-job can run on it, like in the normal yocto pipeline.

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@8d6530f1

post-install: Moved overlay handling to new script

The handling of the overlay arguments has been moved from the
install script to a new post-install script.
The script moves all overlays to /boot/overlays and adds them
to the overlays.txt in the boot directory.
It does so by calling a new shell function "append_overlay" from
gf-prepare-common.

BCS 746-000414
BCS 746-000877

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@6b623986

fng-install:prepare-image: Added dt post-install script

The prepare-dt post-install script detects the board on which it is
running, and sets the devicetree accordingly.

Note: Only works for i.MX6 devices.

BCS 746-000414

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@46b727cc

fng-install: Fixed loading of overlays

Calling the append_overlay function doesn't work, because the
gf-functions script isn't copied into the fng-install script.
As a workaround, we directly write the overlays.txt file.

BCS 746-000414

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@1a47d45c

Merge branch 'dunfell' into rtc_overlays

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@7bb8ca2f

fng-install:prepare-dt: Replaced loop with find

Fixes SC2044

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@844e1dc8

fng-install: Moved loading of overlays back to install

The loading of additional devicetree overlays was moved to an
post-install script. This doesn't work, because the function
downloads the overlays from AP which can't be repeated in
a later update of the system.
The loading of the overlays was moved back to the fng-install
script, but the overlays are now located in /boot/overlays
and they are also activated by adding them to the overlays
variable inside the overlays.txt file.

Note: The append_overlay function was moved to gf-functions,
because it isn't accessible inside the fng-install script,
if it resides in the common post-install functions.

BCS 746-000414

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@5e7f758c

fng-install:post-install: Moved setting of devicetree

Moved the creation of the default devicetree file from prepare-kernel
to prepare-dt.
Removed a duplicate of the devicetree detection for the i.MX6 devices
in the prepare-kernel script.

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@512b8ae3

fng-install:post-install: Added comments to scripts

Extended the documentation and comments in the post-install scripts.

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@03fe573c

prepare-kernel: Set kernel and devicetree in config

Extended the prepare-kernel post-install script by setting the
kernel and the devicetree in the boot configuration.

BCS 746-000877

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@1440b6a0

Merge branch 'dunfell' into rtc_overlays

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@c9948763

fng-install:rtc: Added RTC scripts to prepare-image

The new script was added to the prepare-image recipe.

BCS 746-000877

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@6f993fd0

fng-install:rtc: Added RTC detection for the TANARO

The TANARO will be produced with one of two RTC variants.
We detect the RTC by querying the first register during the
post-install and activate one of two devicetree overlays.

BCS 746-000877

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@0867e1fe

fng-install:prepare-kernel: Removed i.MX8 specific script

The i.MX8 used a custom post-install script for the prepare-kernel
step. Since the default script has been adopted for the i.MX8, the
custom script is removed.

BCS 746-000877

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@ed222c39

fng-install:prepare-image: Added new scripts and clean-up

The new scripts (prepare-overlays and prepare-xml2dto) for the
post-install steps have beend added.
Also wrong indentations have been replaced and the lists have been
sorted.

BCS 746-000877

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@b0d9dca0

fng-install:prepare-kernel: Added i.MX8 support

The default prepare-kernel script didn't support the i.MX8.
Tweaked the script, to support the custom requirements of the i.MX8.
The i.MX6 specific parts for the generation of the overlays (from the
shared XML) and the gf_platform detection has been moved to new scripts.

BCS 746-000877

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@4d23dc39

post-install: Moved overlay handling to new script

The handling of the overlay arguments has been moved from the
install script to a new post-install script.
The script moves all overlays to /boot/overlays and adds them
to the overlays.txt in the boot directory.
It does so by calling a new shell function "append_overlay" from
gf-prepare-common.

BCS 746-000414
BCS 746-000877

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@dcb3ae6e

fngsystem: Added lsb-release to fngsystem

The lsb-release command can be used to query detailed information
regarding the Yocto image/build (from the userspace).

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@a3f2cdfa

packagegroup: Added lsb-release to guf-small

The lsb-release command is used by Lava to query system information.
parent e57f3fce
No related branches found
No related tags found
No related merge requests found
Pipeline #23914 passed with stage
in 10 seconds
......@@ -21,7 +21,7 @@
<project name="meta-freescale.git" revision="5a026be5a6b29a27a7754d7fa5d4765c99f98ed9" remote="fslc" path="sources/meta-freescale" />
<project name="meta-freescale-distro.git" revision="5d882cdf079b3bde0bd9869ce3ca3db411acbf3b" remote="fslc" path="sources/meta-freescale-distro" />
<project name="layers/meta-seconorth-machine" revision="ea29ffa98cafbde15e921ec9c4cf9e8e87b69be7" remote="seco-ne" path="sources/meta-seconorth-machine" />
<project name="layers/meta-seconorth-distro" revision="f7f2be8ed296fb198634a77d89e24ddd4b29f161" remote="seco-ne" path="sources/meta-seconorth-distro" />
<project name="layers/meta-seconorth-distro" revision="82258da2fd04a487244879fbebdb5e2b0b802dd4" remote="seco-ne" path="sources/meta-seconorth-distro" />
<project name="layers/meta-seconorth-nogplv3" revision="5a168457b30d92fcee544c2700b71d7a6f132724" remote="seco-ne" path="sources/meta-seconorth-nogplv3" />
<project name="config" revision="31555dadba7ae8fb291688b5df25a49ffc4c3b2f" remote="seco-ne" path=".conf" >
<linkfile dest="setup-environment" src="setup-environment" />
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment