Skip to content

Integrate meta-seconorth-distro/update-gitlab-ci

Commit: seco-ne/yocto/layers/meta-seconorth-distro@4bba7d38

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.

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@173d6c1b

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-distro@8d4e8fd6

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

Merge request reports

Loading