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

Integrate config/update-gitlab-ci

--

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

--

Commit: config@ea3c622d

bblayers: Removed bblayers for DualEspresso

The bblayers was moved to the custom manifest for the DualEspresso.

--

Commit: config@fec8c556

bblayers: Search for customer configs in manifest

Some customer related projects provide a bblayers inside
the projects manifest. Added a routine to search for these
custom configs. If a custom config was found, use it and
skip our arch based lookup.


(cherry picked from commit 1d3b4ecf7889303a285b990adc04a2a6ee0eb513)
--

Commit: config@30b76b86

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: config@9ff3366c

Integrate gitlab-ci/document-skip-build-label

--

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

Document "skip build" label

--

Commit: config@5479d7fc

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: config@1648ea7d

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

--

Commit: config@21402a86

Integrate gitlab-ci/fix-port-for-lava-tests and 1 more

--

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.

--

Commit: config@2abd2754

Integrate gitlab-ci/rename-to-seconorth

--

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

Rename layers to seconorth

--

Commit: config@61f4ecc4

Integrate gitlab-ci/increase-timeout-for-infrastructure-jobs

--

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

CI: Increase infrastructure timeout to 10min

--

Commit: config@81ba01f5

Integrate gitlab-ci/fix-gitlab-ci-integration

--

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.

--

Commit: config@1d90837f

Integrate gitlab-ci/fix-gitlab-ci-integration and 6 more

--

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

--

Commit: config@58bd07b4

Integrate gitlab-ci/fix-reuse-of-outdated-integration-branch and 2 more

--

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

--

Commit: config@e87f981a

Integrate gitlab-ci/remove-dual-espresso-image-build and 5 more

--

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: config@683204ae

setup: Updated layer-paths to seconorth

--

Commit: config@3b5020eb

setup: Increase niceness to make the build server more responsive

Added a higher niceness level to the local.conf (via the setup script).


(cherry picked from commit 1aefc0e94dc3f088660cb62455e2b031302bcb66)
--

Commit: config@93bb0cbf

layers: Renaming and sorting of layers

The machine and distro layers have been renamed to seconorth.
Also the layer lists have been sorted.

--

Commit: config@1d048e15

describe: Updated git-describe to reflect change to Kirkstone
parent b09fed66
No related branches found
No related tags found
Loading
Pipeline #20831 failed with stage
in 9 seconds
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment