- Jul 28, 2022
-
-
Jonas Höppner authored
When switching from scheme 1 to 2, there was a bug leading to an unformated partition. Additionally I removed the partition message for FT2. This is only used during the yocto installation and was in the wrong position anyway. (cherry picked from commit c0871d1e)
-
Jonas Höppner authored
The implmentation was not really working when used in a yocto installation, as it would have needed a relocation of FNGSystem. Now the explicit change of the partition scheme is only be possible together with the installation of FNGSystem. (cherry picked from commit a4ecd599)
-
Jonas Höppner authored
When FNGSystem 15.1 was just installed and only one partition was setup on the device the installation failed. This is fixed here. Also: in A-B installation mode is the used target (A or B) reported after the installation. (cherry picked from commit e811145d)
-
The nfs-statd systemd service is disabled by default. BCS 746-000876 (cherry picked from commit 96288601)
-
For imx8m it is necessary to specify drm device 0 to run the qt-compositor with eglfs backend. BCS 746-000787 (cherry picked from commit 5058c033)
-
This allows us to draw the progress bar directly on top of the kernel splash logo. By default, psplash only displays the progress bar. BCS 746-000786 (cherry picked from commit ae1922ba)
-
Jonas Höppner authored
Normally we would use network-manager, but for the gplv3 free variants it is not available. In these cases we keep systemd-networkd as network tools available. Also adapt the call to gf-network-conf in the postinsts step during the first boot to automatically determine the used network tooling. This way the configuration for systemd-networkd is generated from the xml setting as needed. Until now the MACAdress was not configured if systemd-networkd was used. Now the MACAddress is added to the newwork config file like it is done when network-manager is used. (cherry picked from commit 91b1c14e)
-
The weston-start script for xwayland overrides the module loading of the notify library. Without notify, Weston doesn't report a successful start back so systemd. As a result, systemd stops Weston after hitting the timeout period. Without the module loading directive in the start script, xwayland needs to be activated in the weston.ini. (cherry picked from commit 510cc193)
-
If x11 and wayland are both activated in the DISTRO_FEATURES, we add xwayland and its xserver implementation to the image. (cherry picked from commit 0c01033f)
-
The tools recipes still use SSH as protocol for the checkout. Since we have opend our repository to the public, SSH isn't available anymore. Because of this, we switch to HTTPS as protocol. (cherry picked from commit e3c2325c)
-
imx6ull uses the linuxfb backend, imx6 and imx8m* using eglfs. (cherry picked from commit e382ac22)
-
(cherry picked from commit bb708bf0)
-
The qt-multi-screen-compositor is based on examples from QT to implement a compositor based on QtWaylandCOmpositor. The implementation is done mostly in qml. (cherry picked from commit 98725129)
-
Jonas Höppner authored
We have now platforms with custom rootfs names in the config. It is easier to install if the correct name is already in the install script. With this change, the image name for the install script can be adapted in a bbappend file. (cherry picked from commit 8fc62521)
-
Jonas Höppner authored
To find the touch the capabilities entries in the sysfs are checked. On Nallino the format contained a space, which made the script exit with error. This change now (hopefully) decodes it correctly. (cherry picked from commit 8ca830a4)
-
Jonas Höppner authored
(cherry picked from commit 548e591f)
-
Previously, iptables was only included via dependencies. (cherry picked from commit 0d782145)
-
Rename the distribution to SECO Northern Europe distribution and reference the manifest as the main source of information. BCS 746-000659 (cherry picked from commit 81bd01a9)
-
We borrow some recipes form public layers. However, most of the public layers are licensed under the MIT license. To make the licenses clear copy the corresponding license files into the relevant directories next to the recipe in question. Recipes in question: - rtl8812au - kbd - beep - mxt-app BCS 746-000658 (cherry picked from commit c402d855)
-
The "initial-draft" branch is deprecated. Use the branch "master" instead. Currently this should not change the content. (cherry picked from commit 32b7490b)
-
According to our company licensing policy for software the Yocto layers should be licensed under the Apache 2.0 license. Adapt the LICENSE-2.0.txt file from https://www.apache.org/licenses/LICENSE-2.0.txt as described in the APPENDIX. Add the license as LICENSE.txt file to the layer repository. BCS 746-000657 (cherry picked from commit d8fabd95)
-
Jonas Höppner authored
The script was relying in the /dev/input/touchscreen link which was not available in FNGSystem previous to version 16. This fix now loops though all available devices and takes the first device with absolute axis.
-
- Jul 12, 2022
-
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@075aeccb Refactoring: share build and test job basics for ci-test and Yocto This shares YAML code for the following procedures: - Build environment - Source code checkout via repo - SSH key and known hosts setup - LAVA test submission - Docker check if build folder is empty
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6508e800 CI: Add hardcoded artifact's path generation also for fng system
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c503a6d4 CI: pipeline yocto: Change scope of CI_PARAM_IMAGE, ... to fix fngsystem build The variables CI_PARAM_IMAGE, CI_PARAM_DISTRO, CI_MACHINE have been defined outside the job in the '.gitlab-ci.yml' file. This has a lower precedence then variables defined inside the job, but it seems that these variables are used in the scope of 'Trigger variables' when available in the trigger job. These override the value set in the template. As main results this made FNGSystem jobs build the normal yocto.
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ea3aa816 CI: Readd allow_failure:true to fix not finished pipelines According to the docs a manual job always has allow_failure set to true, but we see a lot of jobs staying in an unfinished state since the removal of the allow_failure: true keyword for the sdk and test jobs. This should fix the broken behaviour.
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc0503b6 CI: Hardcode the artifacts path in the generated job description Some gitlab update(?) seem to have changed the behaviour in variable passing. In the scripts the variables are available but in the artifacts path does not resolve them any more. May be it has something to do with the introduction of the trigger:forward keyword.
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f39e65ab Manifest: really include yamllint in the full pipeline Previous commit did not have the effect due to wrong extend order.
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0dd147c8 SDK: Remove package step from build sdk, add sdk to artifacts, create deploy_sdk -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ecab2962 Manifest: include yamllint in full pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a4071423 Manifest pipeline: run full build pipeline when triggered via web UI -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8862b213 Manifest refactoring: move job rules into classes This way they can be reused instead of redefining them in each job. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d604b330 Fix wrong remote name in ci-test pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e810c2ac Fix wrong manifest project ID for ci-test pipeline
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@9b8cf51c Share manifest pipeline for ci-test and yocto Combine all common yaml parts in manifest-pipeline.yml and add manifest-pipeline-yocto.yml and manifest-pipeline-ci-test.yml containing the different variable assignments for each environment. This change implicitly introduces parent-child build job generation in the ci-test pipeline, like it is done in the yocto pipeline already. The ci-test build jobs have been moved to build-jobs-ci-test.jinja2 accordingly. Furthermore rename GITLAB_CI_CURRENT_REV to GITLAB_CI_REVISION and remove the run conditions from all generated build jobs, since these are already present in the upstream trigger job. The repos including these files have to be updated with the new file and variable names. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1b939fe Use CI variables in build template directly The job generation script implicitly passes the OS environment to the template, so that the template has access to all GitLab CI variables. Hence there is no need to explicitly pass any of them as command line arguments. This change makes the "generate-build-jobs" job more generic, so that it can be shared with the ci-test pipeline in the future. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@775c09c1 Add gitlab_backup script to download all project exports of a gitlab group
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@7f68f307 Yocto manifest build: re-enable build:merge_request job This job was accidentally disabled in 2e6c1b4, because it was included in the generated child pipeline. This pipeline is not created on the master, though, so the condition for the job was never met. Move the job to the parent pipeline again, so that it gets executed on the master like before. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@970c7fd7 Re-add yamllint stage to ci test manifest pipeline Was accidentally removed in previous commit.
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2b2bc220 Define yamllint job explicitly in each pipeline The yamllint job was included in the pipeline implicitly via the inclusion of common.yml. This is not very transparent. Make the common definition a base job and extend it explicitly in each pipeline now. Add infrastructure stage comment header into both yaml files.
-
- Jun 20, 2022
-
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@686323c6 Remove yaml redundancies in manifest-integration Leave all common yaml parts in manifest-integration.yml and add manifest-integration-yocto.yml and manifest-integration-ci-test.yml containing the different variable assignments for each environment. The repos including these files have to be updated with the new names. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@4c751096 Harmonize manifest-integration yaml files for yocto and ci-test This is the first step for reducing code duplicates. BCS 746-000807 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c877f9c9 retrigger: Allow to specify the manifest's remote identifier in a variable Costum manifest may override this variable
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d9660a80 build-jobs.jinja2: Specify master branch variable again If the MASTER_BRANCH_MANIFEST variable is set in the manifest's .gitlab-ci.yml file, it may not find its way to the generated job, if it is not explicitly set during generation. That is done with this patch.
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2e6c1b4f Build jobs: Use parent-child jobs to generate needed build jobs * Move all build, deploy and test stubs to the manifest-build.yml * Create a new job to generate and trigger the build jobs dynamically * Add the base jinja2 file for the build jobs. * Add initial docs for the manifest pipeline * Remove unused files
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1bc683d5 Move python scripts to subfolder BCS 746-000808
-
- Jun 01, 2022
-
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e6980d48 Update meta-seconorth-dual-espresso path -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@83002e07 accept_merge_request: explicitly check if MR has merge conflicts According to the documentation [1] we should get a 406 error from the API if we try to merge a merge request which has a merge conflict. We are experiencing a different behaviour, though, where we are getting a 405 error in this case. There is an open GitLab issue on this topic [2]. In our error handling we assumed that the reason for a 405 error is most likely a required pipeline which is still running. This assumtion, however, leads to wrong behaviour in cases where no pipeline is started at all. Fixing this now by explicitly checking for merge conflicts at the very beginning of the error handling sequence. [1]: https://docs.gitlab.com/ee/api/merge_requests.html#merge-a-merge-request [2]: https://gitlab.com/gitlab-org/gitlab/-/issues/364102
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0885629d Document "skip build" label
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e514076 Add possibility to skip MR pipeline check via label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ee151673 Add possibility to skip MR pipeline build via label
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ad9d367e Allow check job to fail This makes merging a project MR possible even if the manifest has received new commits since the MR pipeline build has run. The developer is responsible for deciding whether it is safe to merge it without having a build based on the latest manifest. BCS 746-000794 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@81c2ad85 merge_into_manifest: fix error message if MR already exists
-
