summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff.email>2025-03-22 18:00:25 +0100
committerJörg Frings-Fürst <debian@jff.email>2025-03-22 18:00:25 +0100
commit0737819efdd0bae112d16d874cac7e747e43cd08 (patch)
tree98a9ac84f7f347ae530c14852c68870682f3d04c /HACKING
parent163a663518f33bab48b28431972e580b366b4d49 (diff)
parente670957a8693f860cf7d77fed4ce6b4b056a8083 (diff)
Merge branch 'release/debian/1.3-1'debian/1.3-1
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