GitBot authored 2 years ago and Tim Jaacks committed 2 years ago

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6f09c66c

CI: deploy-gitlab-ci: Don't stop integration when one project is already updated

Prior to this change the integration stop when one of the
projects had already the latest ref of gitlab-ci in to submodule.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6c39166f

CI: deploy-gitlab-ci: Don't stop integration when one project is already updated

Prior to this change the integration stop when one of the projects had
already the latest ref of gitlab-ci in to submodule.

--

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

changelog_generator: Use logging instead of print, fix black

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@79afb233

CI: Move changelog_generator to gitlab-ci project

The script can also be run in the normal python container, so this
slightly reduces the complexity.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@383a5aca

Added qt-multi-screen-compositor to project list

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3e88ad8e

buildfng: Moved the image and distro variables to global

The image and distro for the buildfng job can now be set via
global/external variables.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@751fc360

Improve CI documentation

BCS 746-000636

GitBot authored 2 years ago and Tim Jaacks committed 2 years ago

--

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

CI: Add check if integration branch is on top of target branch before reusing it

The integration branch was reused even if there where new commits on the
target branch, which could lead into reverting some changes.
This adds a check, if the existing integration branch is directly based
on the target branch and deletes it if not.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3b5e9be0

CI: Pull new changelog_generator image, add token to the call.

BCS 746-000785

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@968886c0

Update README.md: Add description on the gitlab-ci CI and how to deploy

GitBot authored 2 years ago and Tim Jaacks committed 2 years ago

--

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

CI: Remove build for dual espresso again

The pipeline is not setup to build from different manifest and so on,
and the dual_espresso manifest will probably go to a seperate repo
to keep it private.

--

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

CI: Remove '--verbose' from deploy step

--

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

manifest: Added manifest file selection to ci-test

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@1285aad7

manifest: Added manifest file name to integration script

BCS 746-000518

--

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

build: Added DualEspresso

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@0941262a

layers: Added nogplv3 and dual-espresso layer to CI/CD

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6c3a8ff7

CI:package_release: Remove "GUF-" prefix from gitlab artifacts dir

BCS 746-000637

--

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

manifest-CI: Refactor manifest pipeline files

* Split up build and package steps in separate files
* Add additional comments
* Add log output

BCS 746-000637

--

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

Fix remote name on retrigger stage

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@1ba52853

Move repositories to git.seco.com

Rename variable JENKINSGUF_SSH_PRIVATE_KEY / SSH_PRIVATE_KEY to
GITLAB_PRIVATE_KEY on this occasion, because it contains a private key
that was generated exclusively for this use case. The according public
key has been added as a deploy key in GitLab to all repositories that
this repository needs access to.

Add more detailed documentation concerning this configurationdirectly in
the gitlab-ci files.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3e948f5d

manifest: check if docker build folder is empty

BCS DevOps-000035

--

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

CI: integrate_into_manifest: Fix integration for recipes in SRCREV file

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@976aaec9

CI: deploy_gitlab_ci: Fix merge, integration branch was used after delete

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@65c6f273

CI: Rename foobar to ci-test, like the job names

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@60c311ab

CI: Reuse existing integration branch preserving manual changes

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3318487d

CI: integrate_into_manifest: Fix bug introduced when splitting functions

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@4c74c580

CI: disable 'check' job for gitlab-ci integration as integrate is already disabled

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@5d1fb5c4

CI: Enable MR pipeline for integration of gitlab-ci again

Our settings refuse to merge if no pipeline has been run.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@69d604a4

CI: Fix merge pipeline

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@31d6d7da

CI: deploy_gitlab_ci: Rework the deployment of gitlab-ci into the child projects

The deploy_gitlab_ci now creates the integration commit and branch in
each passed subproject and create an integration commit in the manifest
containing all these new revisions.
A build is then triggered on this commit to test the functionality.

Split the update_submodule functions to reuse them in different ways.
Remove some previously used files.

BCS 746-000740

The distrooverride changed from guf to seconorth, but these recipes
haven't been adapted yet and the syntax was not changed to the new.

Add license information to the REAMDE.md.

BCS 746-000657
BCS 746-000659
BCS 746-000780

- Reformat of recipe
- Removed some extra line breaks and whitespaces

weston is now started as user weston. This leads to a weston socket
in the users runtime dir. To make it possible to start UI tools as
root from the cmdline, this adapts the exported XDG_RUNTIME_DIR to
the new socket location.

The transformation entry in the weston is written by a postinstall script
to reflect the orientation from the xml configuration.
The keywords to specify the rotation have changed with weston 9.0 from
0 to normal
90 to rotate-90
and so on.

The framebuffer could be accessed by a simple write the the /dev/fb0.
This tool allows similar access by piping the data into it and
specifying the connector as parameter.
It also allows to query few things from the drm.

The recipe has a GPLv3 licenses and needs therefore to be moved to the
GPLv3 subgroup.

The install script backups some variables from the existing u-boot
environment before overwriting it. This failed for devices where no
environment was available yet, which lead to stop the update with error.
This case is now ignored and the installation continues without backup
in this case.


(cherry picked from commit a9d370f1)

The i.MX8M uses the meta-freescale layer. The layer adds the
KERNEL_IMAGETYPES to the IMAGE_BOOT_FILES. This breaks the copy
operation in the do_collect_files function because we don't handle
the kernel together with the boot files.
The issue is fixed by creating a copy of the IMAGE_BOOT_FILES, removing
the KERNEL_IMAGETYPES and using the copy in the function.

Since Kirkstone, there is a new way of disabling symlinks of the boot
artifacts (kernel, etc.): To disable the creation of these links, the
variable KERNEL_IMAGETYPE_SYMLINK  can be set to 0. Since we use a FAT
boot partition, links in the boot folder of the image lead to errors during
the extraction of the image and we have to disable them. However, the new
variable also disables the creation of links for the devicetrees and kernel
in the deploy folder.
To solve errors during the package of Flash-N-Go-System, the copy operations
for the boot files and kernel have been changed.

The fng-install scripts have been updated to reflect the new
image names.

The distros have been renamed to seconorth.
Also some clean-up, sorting and commenting was done.

Images have been renamed to seconorth.
Additionally, some clean-up and commenting has been done.

Renamed the guf part of the packagegroups to seconorth.
Also some clean-up and sorting of the groups has been done.

Also updated the URLs to www.seco.com.

The kernel isn't supposed to be part of the Flash-N-Go-System
ramfs. Since Kirkstone, the old way of removing the kernel doesn't
work anymore. With the PACKAGE_EXCLUDE, the kernel is excluded from
the do_rootfs step.

The native class must be included last, to prevent unexpected
behaviour.

The feature-check isn't used in the minimal image. Yocto shows a warning
because of this, so we remove the include from the minimal image and
move it to the standard/small images.

Some recipes are renamed based on the device arch.
To prevent this, the arch must be set before including the packagegroup
class.

- Removed unused code
- Fixed format and general code clean-up
- Fixed missing branch warning in SRC_URI

- Clean-up of the Flash-N-Go recipe
- Removed old code parts, that are no longer valid
- Excluded the Kernel from the initramfs, because its too big

Via the gplv3 distro feature, GPLv3 software can be enabled/disabled.
The new variant is build without GPLv3 software.
Also removed duplicate pam entry in DISTRO_FEATURES of regular
wayland distro.

The inclusion of the GPLv3 packages was broken.
With the changes, GPLv3 packages are only build/included, when the
gplv3 feature is set in DISTRO_FEATURES.

Also fixed wrong spelling in recipe name.

The beep recipe was backported to Dunfell. There is an upstream beep
recipe for Kirkstone, so we don't need our custom recipe anymore.

We upgraded kbd to a newer version because of build errrors in Yocto.
Poky now provides the same version we upgraded to, so no need for a custom
version anymore.