summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff.email>2024-10-20 15:21:43 +0200
committerJörg Frings-Fürst <debian@jff.email>2024-10-20 15:21:43 +0200
commit4682deeb62247d34de87f8e777f99e2d337fd377 (patch)
tree5bd5b5605b5f3a4b3c8ea7468c34c23094afdef4 /HACKING
parent00893e79fc62966067af1a106567db96bd170338 (diff)
New upstream version 1.3upstream/1.3upstream
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING9
1 files changed, 7 insertions, 2 deletions
diff --git a/HACKING b/HACKING
index 9edbdfd6..20c9abc6 100644
--- a/HACKING
+++ b/HACKING
@@ -104,10 +104,15 @@ To speed up the build:
Continuous integration
======================
-The package is built automatically, at regular intervals. You find the latest
-build results here:
+There are two continuous integrations that regularly build and test
+libunistring:
+* On a Linux/glibc system only:
https://gitlab.com/gnu-libunistring/ci-distcheck/pipelines
https://gitlab.com/gnu-libunistring/ci-distcheck/-/jobs?scope=finished
+ This one will catch only the most blatant mistakes.
+* On many platforms:
+ https://github.com/gnu-libunistring/ci-check/actions
+ This one catches platform-specific bugs.
Running the testsuite in valgrind