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

--

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

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

--

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

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

--

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.

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

--

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 2 years ago and Tim Jaacks committed 2 years ago

--

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

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

--

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.

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

--

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

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

--

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

Move python scripts to subfolder

BCS 746-000808

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

--

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

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

--

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

Document "skip build" label

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

--

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 2 years ago and Tim Jaacks committed 2 years ago

--

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

The SRC_URI of the various tools are still using SSH.
With the opening of our repositories, SSH isn't available for checkout
anymore. Because of this, we changed the protocol to HTTPS instead.

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

--

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

CI: Add fake lava test to ci-test, reduce fetch depth in update submodule

--

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

CI: Add variable containing the port for ssh access of the gitlab instance

Our server installation uses port 4444 for ssh access. The lava tests
didn't took this into account.

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

--

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

Rename layers to seconorth

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

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@67b0195a

CI: Increase infrastructure timeout to 10min

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

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d2210b6

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.

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.