OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci/farms: always compare the code against main repository

Browse Source 
`rules:changes:compare_to` resolved firstly pushed branch pipelines,
which always evaluated `rules:changes` as true which breaks the workflow

Since we now explicitely say, that we compare against `main` repository,
GitLab can evaluate against real changes.

Fixes: 79f7882fc6 ("ci: add quirk for GitLab assuming changes is always true for scheduled runs")

Reviewed-by: Eric Engestrom <eric@igalia.com>
Signed-off-by: David Heidelberg <david.heidelberg@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24305>
This commit is contained in:
David Heidelberg
2023-07-24 18:27:02 +02:00
parent 50c29e1ffa
commit 7b29ae557a
2 changed files with 89 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/releasing.rst
View File

@@ -228,6 +228,14 @@ Now go to
`GitLab <https://gitlab.freedesktop.org/mesa/mesa/-/milestones>`__ and
add the new Mesa version X.Y.
Now you need to adjust CI, to not try to compare the changed files against `main` branch.
.. code-block:: console
sed -i '/compare_to: main/d' .gitlab-ci/**/*.yml
git commit -asm 'ci: disable comparing against the main branch'
Check that there are no distribution breaking changes and revert them if
needed. For example: files being overwritten on install, etc. Happens
extremely rarely - we had only one case so far (see commit