- Jul 30, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@b96b806b kernel:mx8m: Activated VPU related modules/drivers Activated/Enabled modules/drivers that might be related to the Hantro VPU and DRM. -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@9ac4ff01 machine:mx8m: Updated preferred gstreamer version 1.18.5 Set the preferred gstreamer version for the i.MX8M devices to 1.18.5. -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@d9b7acce machine:mx8m: Clean-up of preferred kernel The mx8mm had a duplicate definition of the preferred kernel provider and version. Also the preferred version in the include for the i.MX8 devices has been changed to the correct name (linux-imx). -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@99ac77f6 kernel:config: Moved kernel defconfig to correct folder The defconfig for the 5.15.5 kernel is used by the mx8mm and mx8mp. The location "imx8mguf" is only accessible by the mx8mm. To make the config available to the mx8mp, the config folder was renamed. Note: imx8mguf is the machine name of the mx8mm. This is a known bug and will be fixed in the future. -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@87004629 kernel:mx8m: Set the active kernel to 5.15.5 For the i.MX8 devices, we use the 5.15.5 Yocto kernel provided by NXP. -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@b02d1671 machine:mx8m:dt: Fixed the devicetrees for mx8mm/mx8mp In Yocto Kirkstone, we use the 5.15.5 kernel from NXP for the i.MX8 devices. In the kernel repository we moved all G&F and K&K devicetrees to a new folder called seconorth. Edit the machine configurations to reflect this change and build the correct devicetrees.
-
- Jul 29, 2022
-
-
GitBot authored
-- Commit: seco-ne/kernel/linux-imx-kuk@3b8c56b6 dt:seconorth: Added trizeps8mini_atm700 to Makefile
-
GitBot authored
-- Commit: seco-ne/kernel/linux-imx-kuk@0672e1d3 dts: Added missing devicetrees for Trizeps 8 Mini -- Commit: seco-ne/kernel/linux-imx-kuk@41aa9fa9 dts: Added devicetree for Trizeps 8 Mini and pConXS
-
GitBot authored
-- Commit: seco-ne/kernel/linux-imx-kuk@a2b8df11 dts: Apply changes to mx8mp from 5.10 kernel
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@597c7a49 fng-system: slightly increase INITRAMFS_MAXSIZE The build for the imx8mpguf hit the limit. -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@29f0f098 fng-install: Fixed setting of custom devicetree The post-install steps for setting a custom devicetree have been changed for the i.MX8 devices. For the custom devicetree to work again, the name of the devicetree needs to be written to the devicetree file in the boot partition. BCS 746-000877 (cherry picked from commit 714adb35316565cdb97da046bda41ff2ccce7519) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@e1136a4e qtbase: Add gif To add qgif to the Qt environment add the gif PACKAGECONFIG. (cherry picked from commit cd3c70f1e6e9c779f515aaf55d80c32240965e12) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@4c67d8a8 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 (cherry picked from commit 40d7ba85d58160c91f4a7e41d59240c713bf3508) 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-000414 BCS 746-000877 (cherry picked from commit 3edf9fc8ef6fc790cc509e3ccd756232a569df47) 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 (cherry picked from commit 3a397d4448ace2dbdfcb3c63ad5d90e75a3ec1cb) 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 (cherry picked from commit 32b8f0c20331a3aff6b6e77a0576b755fdcfc2d6) fng-install:post-install: Added comments to scripts Extended the documentation and comments in the post-install scripts. (cherry picked from commit c14d978b516e9b45c7bb292d6838744dbe75c27c) fng-install:prepare-dt: Replaced loop with find Fixes SC2044 (cherry picked from commit 2cc3f5397c55cd7b5bab7ba41ffc052d007b87c0) fng-install:prepare-image: Convert recipe's syntax to kirkstone -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@b8c69230 post-install: Rework and fix of overlay handling Overlays that have been installed by Yocto are now moved into /boot/overlays. This is due to the inability of Yocto to easily handle devicetree overlays during the build. Overlays that are provided via the parameters of fng-install (--DTBO) are also placed inside /boot/overlays. Additionally, they are appended to the overlays variable inside the overlays.txt file. The overlays.txt file is parsed during the prepare-kernel post-install step. The loaded overlays are then applied to the default devicetree. BCS 746-000414 BCS 746-000877 (cherry picked from commit 5f97c8e6844897ad4cb45a81e6ee21e831e0ada6) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@ba006a1d 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). (cherry picked from commit 883e6834afc1173e2c41ed5175bc53f56c0c4010) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@8002b0cf packagegroup: Added lsb-release to guf-small The lsb-release command is used by Lava to query system information. (cherry picked from commit f584eef64ec4cb7f914d9f21bcba110cc50cf2af) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@98e330cc FNGSystem: Install kernel-modules to fix missing sound support We did remove the kernel modules for FNGSystem to reduce the image size. Compared to FNGSystem 27 the kernelmodules are adding about 2 MB, which seems to be OK for me. (cherry picked from commit 38c8f73c9756c9bee5e80a758800acdc27ab1d8e) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@0f489a5b shared-conf: Allow on/off for bool values not only true/false (cherry picked from commit f940734562f35df72c630f44421edb19c58927dc) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@b89357c0 fnginstall-postinstallation: Fix boot partition detection for fngsystem The scripts failed if run in an installed fngsystem. This is needed in FT2, when new xml files are installed after the FNGSystem installation. (cherry picked from commit 920b5c91fbb3bb8a63abf2bb506d761fd1b083e4) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@fa41aa9f alsa:imx6: Switch to sgtl5000 as default audio card Replaced absolute card number by the ID of the sgtl5000 audio card. Added additional alsa configuration files for imx6ull as it does not have the sgtl5000 codec. BCS 746-000548 (cherry picked from commit b3c8ca1b65107f78289fa8d97875b802276a6565) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@e7916d32 multiscreen-compositor: Adapt receipe to adapted naming, add message client Also convert recipe's syntax to kirkstone (cherry picked from commit 984094770d6ecf53270bb223954ac6aa4e4f5b10) (cherry picked from commit 325cd3c2b1201ff9580137285878245fee6af08b) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@f80c2721 fng-install: Fix --partition-scheme change in FNGSystem install script 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 c0871d1ef6cc397ce704c90291a84234613cdb57) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@bb7173fa fng-install: Move the partition-scheme parameter to the fngsystem install script 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 a4ecd59956117a6703e8b9a735185558878ff9c6) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@6a7b1727 fng-install: Fix installation issue when used with fresh FNGSystem 15.1 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 e811145db8146087fe25a6a9aed6c9e98c2566aa) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@f4bd9d7a NFS: Add nfs-utils-client package to image The nfs-statd systemd service is disabled by default. BCS 746-000876 (cherry picked from commit 962886013567aca13487cea3997ba43d7851327e) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@6875c379 qt-multi-screen-compositor: Add kms.conf for imx8m 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 5058c033894505ab86cd01ca45279be6ff83461c) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@88c8205c psplash: Added switches for clear-background, logo and progress border 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 ae1922ba8ddaa597bec22a7d1b5d11d397009e5e) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@4362b2c7 systemd: Remove networkd depending on gplv3 in DISTRO_FEATURE, configure MAC Address 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 91b1c14e0fca97352ec7e1fb4b42c0baf9cfaa51) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@5f2b57f0 xwayland: Fixed timeout during start-up 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 510cc1933f49038f36fc19e3b58822312e44ea76) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@6fbad68a packagegroup: Added optional xwayland to graphics group 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 0c01033f51d3f7e8569f3c337040a1205b5958fb) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@a9b5c766 git: Changed protocol to HTTPS 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 e3c2325cd10c6097b863121fe66e07d0062a7d18) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@e83188e9 qt-multi-screen-compositor: Add systemd units for imx6ull and the other platforms imx6ull uses the linuxfb backend, imx6 and imx8m* using eglfs. (cherry picked from commit e382ac22e5e6685f47f72be454632bf9935cc975) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@26ba9fdd Add qt-multi-screen-compositor to packagegroup-graphics (cherry picked from commit bb708bf0ced423bba09edd3edfcbd8f73975eb37) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@fea2666e Add qt-multi-screen-compositor recipe as alternative to weston 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 98725129ad3f0600b910a938ca9d80544ac1eae8) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@70fa62f6 fng-install: Insert the image name during deploy 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 8fc625212ec728898118118da8924f68b94334c3) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@78102b62 touchcalibration: Fix decode of sysfs input dev capabilities entry 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 8ca830a4a9778ee838c4a2cd2064f0bf5089b610) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@0b2283b4 Tools: Add fbgrab to packagegroup tests to allow screenshots from framebuffer. (cherry picked from commit 548e591fa2f95562521bde845373674fb898ce6e) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@0bcd7770 packagegroup-networking: Add iptables Previously, iptables was only included via dependencies. (cherry picked from commit 0d782145f79dabfc6bb0741e29395a96160cf4eb) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@11c96661 README: Adapt the README for SECO 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 81bd01a9f04b974ca44acbef6487d62118dd9d5d) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@09baf9e0 LICENSE: Add licenses for copied recipes 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 c402d855fc8d47e3742ada3b0a3fda4b9649e414) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@c4c75f20 gfeeprom: Pull the master branch instead of initial-draft The "initial-draft" branch is deprecated. Use the branch "master" instead. Currently this should not change the content. (cherry picked from commit 32b7490b943d662047901d4c95e1342000daf210) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@df5d98f8 LICENSE: Add Apache 2.0 license file 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 d8fabd955097b7a30f4bfc8b82001f00c904dc21) -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@9890e216 touch calibration: Fix creation of libinput calibration data during installation 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 28, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@819fdb21 linux-imx: Adapt comment to to new override syntax -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@917cd74d linux: defconfig: imx6ull: Add GPIO and PWM beeper as module Add support for GPIO and PWM beepers. This enables the on-board beeper on the SECO Northern Europe NALLLINO platform. BCS 746-000992 (cherry picked from commit ad7371e069ae0cd3c706fe635c272cfad29d8984) -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@423c00c2 mxt-touch: Pull support for atmel mxt touch from dunfell branch * imx6:mxt-touch: Add kernel support for atmel mxt touch BCS 746-000886 (cherry picked from commit 82cbcf67a86c10ea3719637ae7b4e87fe58d0944) * maxTouch:udev: Add udev rule to skip maxTouch fwr loading fallback The current version of the atmel_mxt_ts driver tries to load a controller configuration on each driver probe. However, if no config is provided or can't be provided because the driver is built-in, the driver probing process is delayed by 60 seconds because of a sysfs firmware load fallback. Added a udev rule that automatically cancels the sysfs firmware fallback. BCS 746-000892 (cherry picked from commit 55a34692b3cff31cb0f9ca3a400af843fa74f0b8) * atmel-mxt: convert recipe to new syntax -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@6fc965a0 bootscript:dt: Added devicetree description file for i.MX8 Added an description file with the default devicetree for i.MX8 devices. The file is parsed/used by the post-install scripts to generate the boot configuration. BCS 746-000877 (cherry picked from commit 283c6dfbad04132827135106bbc207393337500d) -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@cf9b0316 bootscripts: Clean-up and reformat Changed the copyright and URL in the bootscript recipes. Also did a clean-up/reformat of the recipes. (cherry picked from commit ba9e87ec884254967466f4a4dc1d9dd93063c33b) -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@38bb5a81 machine:tanaro: Added RTC overlays In the future, the TANARO will be produced with two possible RTC variants. Both variants are present in the main devicetree but are disabled by default. During the installation, one of the RTCs will be activated via one of the two devicetree overlays. BCS 746-000877 (cherry picked from commit df176aaef0f5eb459ea995bafb19a79a895b6a97) -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@e0c864d8 machine: Clean-up of i.MX8MM machine Also small changes to the Kernel include file. (cherry picked from commit 49cec4414dda982596e32c16a9ee0cba908856cc) -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@5517bf25 SIS: Fix touch-up issue Sometimes we get no touchup signal in Qt. This was seen with the QML drag-and-drop example. Looking at the output of evtest of the sis input device, you see different behavior for a working and a missing touch-up. Failed: <pre> ... Event: time 1587646331.383580, type 3 (EV_ABS), code 0 (ABS_X), value 2365 Event: time 1587646331.383580, type 3 (EV_ABS), code 1 (ABS_Y), value 2894 Event: time 1587646331.383580, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2365 Event: time 1587646331.383580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 2894 Event: time 1587646331.383580, -------------- SYN_REPORT ------------ Event: time 1587646331.402073, type 3 (EV_ABS), code 0 (ABS_X), value 2367 Event: time 1587646331.402073, type 3 (EV_ABS), code 1 (ABS_Y), value 2887 Event: time 1587646331.402073, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 0 Event: time 1587646331.402073, type 3 (EV_ABS), code 58 (ABS_MT_PRESSURE), value 0 Event: time 1587646331.402073, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2367 Event: time 1587646331.402073, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 2887 Event: time 1587646331.402073, -------------- SYN_REPORT ------------ </pre> Good <pre> Event: time 1587646407.907930, -------------- SYN_REPORT ------------ Event: time 1587646407.922769, type 3 (EV_ABS), code 0 (ABS_X), value 790 Event: time 1587646407.922769, type 3 (EV_ABS), code 1 (ABS_Y), value 1747 Event: time 1587646407.922769, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 790 Event: time 1587646407.922769, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 1747 Event: time 1587646407.922769, -------------- SYN_REPORT ------------ Event: time 1587646407.945577, type 3 (EV_ABS), code 0 (ABS_X), value 840 Event: time 1587646407.945577, type 3 (EV_ABS), code 1 (ABS_Y), value 1918 Event: time 1587646407.945577, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 840 Event: time 1587646407.945577, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 1918 Event: time 1587646407.945577, -------------- SYN_REPORT ------------ Event: time 1587646407.968810, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 0 Event: time 1587646407.968810, type 3 (EV_ABS), code 58 (ABS_MT_PRESSURE), value 0 Event: time 1587646407.968810, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1587646407.968810, -------------- SYN_REPORT ------------ </pre> It seems that the @ABS_MT_TRACKING_ID value -1@ is missing somehow. This might be the case when the driver sends a valid coodinate but also states that the pressure is 0. Fix this by sending a touch-up (all ABS_PRESSUE, ABS_MT_PRESSURE, and ABS_BUTTON 0 and ABS_MT_TRACKING_ID -1) when pressure is 0. BCS 746-000871 (cherry picked from commit 0326de4b2c2a5ca6e52b84e0bfe12f88123aeedd) -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@034d5b83 mxt-touch: Add kernel support for atmel mxt touch BCS 746-000857 (cherry picked from commit 4bf6746db6f04702f190840b24f152c703bc162e) -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@848013cb linux-guf:imx6ull: Add MQS and simple-amplifier Add the iMX Medium Quality Sound driver and the simple amplifier driver to the defconfig. Together with the latest kernel changes for NALLINO this adds sound support for the NALLINO board. BCS 746-000796 (cherry picked from commit 69fb720b1d7920bb0ad7235d08b9be7162117ad5) -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@420c6a1b LICENSE: Add Apache 2.0 license file 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 66d98abb1b077a421da78edc6ec35643ac00b852)
-
GitBot authored
-- Commit: seco-ne/kernel/linux-imx-kuk@319aaa07 dts:seconorth: Fix makefile -- Commit: seco-ne/kernel/linux-imx-kuk@e3988a18 tanaro:rtcs: Fix to RTC overlay mechanism The first approach of selecting a RTC didn't work as expected. The active RTC must reside on the rtc0 alias because otherwise the hwclock utilities can't access the RTC. For this to work, we now have a placeholder in the main device tree that is filled with the actual values in one of the two overlays. This breaks with the naming conventions for I2C bus devices, but right now, we don't have a better solution. BCS 746-000877 (cherry picked from commit 11963a85cfe1299828e37e6f1c007e83bd4911e4) -- Commit: seco-ne/kernel/linux-imx-kuk@35d0ab2c tanaro:rtcs: Added overlays for the TANARO RTCs The TANARO will be produced with one of two RTC variants. One of them will be activated during the installation by applying one of the overlays. BCS 746-000877 (cherry picked from commit 9b1710b28582ce4b4280d753d32a2186a46d8b10)
-
GitBot authored
-- Commit: config@d3eac486 LICENSE: Add Apache 2.0 license file 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 21df2bf31565551a8d9a2827ed1ae2530f5d6fa1)
-
(cherry picked from commit f84daeff)
-
Jonas Höppner authored
Due to the usage of CI files from gitlab-ci repo, these local files are not used any more. Change-Id: Ia9c2f5a8d2c928f9567c7ead0093b5d446c69dc1 (cherry picked from commit 8c48431c)
-
Jonas Höppner authored
Change-Id: I30e9f4f850615cfee33798435124f0fc9b145b8f
-
- Jul 27, 2022
-
-
GitBot authored
-- Commit: seco-ne/kernel/linux-imx-kuk@baafbb4e dts: Replaced imx8mp and imx8mp-pinfunc Replaced imx8mp-pinfunc.h and imx8mp.dtsi with the files provided with the 5.15 kernel. -- Commit: seco-ne/kernel/linux-imx-kuk@29cb78fb dts: Fixed subdir in Makefile Our devicetrees reside in the seconorth sub-directory. -- Commit: seco-ne/kernel/linux-imx-kuk@29f05d7f dts: Added missing include and edited Makefile Added missing devicetree include and added the new devicetrees to the Makefile. -- Commit: seco-ne/kernel/linux-imx-kuk@99eb8579 dt: Added devicetrees for pConXS and Trizeps 8 Plus The devicetrees and includes have been copied from the linux-5.10.9-guf branch.
-
Jonas Höppner authored
Add the meta-gplv2 layer to the manifest and download it by default. Without the addition to the bblayers.conf it will not be used.
-
- Jul 13, 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.
-
-- 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
-
* The master branch manifest needs to be specified here, as the kirkstone branch includes the same files and needs to use kirkstone as master branch manifest * The project id needs to be specified here, as the 'manifest.yml' will be included in multiple manifest repos with different ids. * Putting the gitlab-ci-rev into a variable allows it to use it in further ci steps. The 'deploy-gitlab-cy' step of the gitlab-ci repo should update this value as well, as a plain substitution of the hash is used.
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@3c880db4 Integrate gitlab-ci/share-build-and-test-job-basics -- 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/layers/meta-seconorth-machine@180fb023 Integrate gitlab-ci/CI-hardcoded-artifact-path-for-fngsystem -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6508e800 CI: Add hardcoded artifact's path generation also for fng system -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@9e57f620 Integrate gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more -- 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/layers/meta-seconorth-machine@e8fed12b Integrate gitlab-ci/CI-readd-allow-failure-true -- 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/layers/meta-seconorth-machine@ce63d1ef Integrate gitlab-ci/test-artifact-upload -- 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/layers/meta-seconorth-machine@f854a078 Integrate gitlab-ci/really-include-yamllint-in-manifest-pipeline -- 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/layers/meta-seconorth-machine@7be7421e Integrate gitlab-ci/sdk-deployment and 5 more -- 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/layers/meta-seconorth-machine@cfa6b992 Integrate gitlab-ci/share-manifest-pipeline and 2 more -- 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/layers/meta-seconorth-machine@f3add766 Integrate gitlab-ci/fix-build-merge-request-job and 1 more -- 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/layers/meta-seconorth-machine@1427c222 Integrate gitlab-ci/define-yamllint-explicitly -- 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.
-
- Jul 12, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@546c2e50 Integrate gitlab-ci/share-build-and-test-job-basics -- 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/layers/meta-seconorth-nogplv3@22280218 Integrate gitlab-ci/CI-hardcoded-artifact-path-for-fngsystem -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6508e800 CI: Add hardcoded artifact's path generation also for fng system -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@e13c13f6 Integrate gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more -- 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/layers/meta-seconorth-nogplv3@db904b0d Integrate gitlab-ci/CI-readd-allow-failure-true -- 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/layers/meta-seconorth-nogplv3@12305175 Integrate gitlab-ci/test-artifact-upload -- 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/layers/meta-seconorth-nogplv3@4735f8e8 Integrate gitlab-ci/really-include-yamllint-in-manifest-pipeline -- 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/layers/meta-seconorth-nogplv3@9b09b336 Integrate gitlab-ci/sdk-deployment and 5 more -- 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/layers/meta-seconorth-nogplv3@eef5e74b Integrate gitlab-ci/share-manifest-pipeline and 2 more -- 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/layers/meta-seconorth-nogplv3@1a101b88 Integrate gitlab-ci/fix-build-merge-request-job and 1 more -- 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/layers/meta-seconorth-nogplv3@0a8c7287 Integrate gitlab-ci/define-yamllint-explicitly -- 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.
-
GitBot authored
-- Commit: config@1cc9dc24 Integrate gitlab-ci/share-build-and-test-job-basics -- 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: config@231e7779 Integrate gitlab-ci/CI-hardcoded-artifact-path-for-fngsystem -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6508e800 CI: Add hardcoded artifact's path generation also for fng system -- Commit: config@09802c91 Integrate gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more -- 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: config@b291be02 Integrate gitlab-ci/CI-readd-allow-failure-true -- 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: config@64e3daf5 Integrate gitlab-ci/test-artifact-upload -- 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: config@8b327116 Integrate gitlab-ci/really-include-yamllint-in-manifest-pipeline -- 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: config@a8afe589 Integrate gitlab-ci/sdk-deployment and 5 more -- 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: config@a75ce824 Integrate gitlab-ci/share-manifest-pipeline and 2 more -- 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: config@143834e3 Integrate gitlab-ci/fix-build-merge-request-job and 1 more -- 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: config@1348b682 Integrate gitlab-ci/define-yamllint-explicitly -- 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.
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@8311c0f1 Integrate gitlab-ci/share-build-and-test-job-basics -- 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/layers/meta-seconorth-distro@8046ca4c Integrate gitlab-ci/CI-hardcoded-artifact-path-for-fngsystem -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6508e800 CI: Add hardcoded artifact's path generation also for fng system -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@fdc5d26c Integrate gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more -- 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/layers/meta-seconorth-distro@5b86ebf2 Integrate gitlab-ci/CI-readd-allow-failure-true -- 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/layers/meta-seconorth-distro@97fba070 Integrate gitlab-ci/test-artifact-upload -- 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/layers/meta-seconorth-distro@5714ff50 Integrate gitlab-ci/really-include-yamllint-in-manifest-pipeline -- 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/layers/meta-seconorth-distro@01508ffe Integrate gitlab-ci/sdk-deployment and 5 more -- 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/layers/meta-seconorth-distro@ffed82d0 Integrate gitlab-ci/share-manifest-pipeline and 2 more -- 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/layers/meta-seconorth-distro@28c5fe8e Integrate gitlab-ci/fix-build-merge-request-job and 1 more -- 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/layers/meta-seconorth-distro@6a04cf81 Integrate gitlab-ci/define-yamllint-explicitly -- 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
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@1f71143f Integrate gitlab-ci/share-yaml-code-for-manifest-integration and 2 more -- 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/layers/meta-seconorth-nogplv3@6d040847 Integrate gitlab-ci/set-master-branch-manifest-in-jinja2 -- 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/layers/meta-seconorth-nogplv3@ac0b8e04 Integrate gitlab-ci/use-parent-child-build-jobs -- 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/layers/meta-seconorth-nogplv3@ea9a9bc5 Integrate gitlab-ci/move-python-scripts-to-subfolder -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1bc683d5 Move python scripts to subfolder BCS 746-000808
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@4f158f41 Integrate gitlab-ci/share-yaml-code-for-manifest-integration and 2 more -- 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/layers/meta-seconorth-distro@0219cbc7 Integrate gitlab-ci/set-master-branch-manifest-in-jinja2 -- 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/layers/meta-seconorth-distro@0af24422 Integrate gitlab-ci/use-parent-child-build-jobs -- 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/layers/meta-seconorth-distro@ea28c1fe Integrate gitlab-ci/move-python-scripts-to-subfolder -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1bc683d5 Move python scripts to subfolder BCS 746-000808
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@6593e178 Integrate gitlab-ci/share-yaml-code-for-manifest-integration and 2 more -- 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/layers/meta-seconorth-machine@5ed67733 Integrate gitlab-ci/set-master-branch-manifest-in-jinja2 -- 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/layers/meta-seconorth-machine@24abc379 Integrate gitlab-ci/use-parent-child-build-jobs -- 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/layers/meta-seconorth-machine@85183ffd Integrate gitlab-ci/move-python-scripts-to-subfolder -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1bc683d5 Move python scripts to subfolder BCS 746-000808
-
GitBot authored
-- Commit: config@b40f13f9 gitlab-ci: set branch variables to kirkstone -- Commit: config@e3625d06 Integrate gitlab-ci/share-yaml-code-for-manifest-integration and 3 more -- 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: config@ee635b23 Integrate gitlab-ci/use-parent-child-build-jobs -- 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: config@a06c5a58 Integrate gitlab-ci/move-python-scripts-to-subfolder -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1bc683d5 Move python scripts to subfolder BCS 746-000808
-
- Jun 02, 2022
-
-
Tobias Kahlki authored
The DualEspresso manifest was moved to a custom project. We remove it therefore from the main manifest.
-
- Jun 01, 2022
-
-
GitBot authored
-- Commit: https://git.seco.com/seco-ne/yocto/custom/dual-espresso/meta-seconorth-dual-espresso/-/commit/bc4bd90cc229524bc2d9dcc2eed061845f37faca Integrate gitlab-ci/update-dual-espresso-path and 1 more -- 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: https://git.seco.com/seco-ne/yocto/custom/dual-espresso/meta-seconorth-dual-espresso/-/commit/a06802d3dd89c07ac8446c96ee028c2ae9b770c8 Integrate gitlab-ci/document-skip-build-label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0885629d Document "skip build" label -- Commit: https://git.seco.com/seco-ne/yocto/custom/dual-espresso/meta-seconorth-dual-espresso/-/commit/6b1d6b2e1106b0e984af2f2b9b0d1b8f0202b3dd Integrate gitlab-ci/skip-check-via-label and 1 more -- 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: https://git.seco.com/seco-ne/yocto/custom/dual-espresso/meta-seconorth-dual-espresso/-/commit/6c8e4274aab48a03f450ac7d3eafb6a21035aee1 Integrate gitlab-ci/allow-check-job-to-fail and 1 more -- 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
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@1c6ef2d6 Integrate gitlab-ci/update-dual-espresso-path and 1 more -- 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/layers/meta-seconorth-machine@8f596afd Integrate gitlab-ci/document-skip-build-label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0885629d Document "skip build" label -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@4ffb20b0 Integrate gitlab-ci/skip-check-via-label and 1 more -- 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
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@67f7c664 Integrate gitlab-ci/update-dual-espresso-path and 1 more -- 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/layers/meta-seconorth-nogplv3@1f9478df Integrate gitlab-ci/document-skip-build-label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0885629d Document "skip build" label -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@b26456f2 Integrate gitlab-ci/skip-check-via-label and 1 more -- 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
-