summary refs log tree commit diff stats
path: root/docs/devel
diff options
context:
space:
mode:
authorDaniel P. Berrangé <berrange@redhat.com>2023-06-08 17:40:15 +0100
committerThomas Huth <thuth@redhat.com>2023-06-26 08:58:02 +0200
commit1ddd2ff9cd873dd7d634a0b6296e91c6583b47e3 (patch)
tree136d82c2c1c30af1896a7370f49f23432cfbde05 /docs/devel
parentd4c7a56539d0bdb6fccf60af94d528613cbc7c4b (diff)
downloadfocaccia-qemu-1ddd2ff9cd873dd7d634a0b6296e91c6583b47e3.tar.gz
focaccia-qemu-1ddd2ff9cd873dd7d634a0b6296e91c6583b47e3.zip
gitlab: allow overriding name of the upstream repository
The CI rules have special logic for what happens in upstream. To enable
contributors who modify CI rules to test this logic, however, they need
to be able to override which repo is considered upstream. This
introduces the 'QEMU_CI_UPSTREAM' variable

  git push gitlab <branch> -o ci.variable=QEMU_CI_UPSTREAM=berrange

to make it look as if my namespace is the actual upstream. Namespace in
this context refers to the path fragment in gitlab URLs that is above
the repository. Typically this will be the contributor's gitlab login
name.

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Michael Tokarev <mjt@tls.msk.ru>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20230608164018.2520330-3-berrange@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'docs/devel')
-rw-r--r--docs/devel/ci-jobs.rst.inc6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/devel/ci-jobs.rst.inc b/docs/devel/ci-jobs.rst.inc
index f72537853b..3f6802d51e 100644
--- a/docs/devel/ci-jobs.rst.inc
+++ b/docs/devel/ci-jobs.rst.inc
@@ -75,6 +75,12 @@ in a handful of namespaces
    'latest', but if running pipelines for different branches
    concurrently, it should be overridden per pipeline.
 
+ * QEMU_CI_UPSTREAM - gitlab namespace that is considered to be
+   the 'upstream'. This defaults to 'qemu-project'. Contributors
+   may choose to override this if they are modifying rules in
+   base.yml and need to validate how they will operate when in
+   an upstream context, as opposed to their fork context.
+
  * nnn - other misc variables not falling into the above
    categories, or using different names for historical reasons
    and not yet converted.