• .gitlab-ci-unix.yml

    From Deucе@VERT to Git commit to main/sbbs/master on Thu Dec 11 22:06:47 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/261a5dd2b2932b46a2eea9f5
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    Use git clone strategy for cleanup

    We don't actually need a git copy here, but it looks like using
    GIT_CLONE is the only way to have the gitlab-runner jobs delete the
    project directory afterward.

    Hopefully, this allows us to avoid infinately growing storage for
    a runner.

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Thu Dec 11 22:21:46 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/5f68f35179dd0ab1eaf47028
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    Use GIT_STRATEGY: empty instead of none

    This ensures the build dir doesn't have the git "stuff" in it for
    these jobs... which will help keep storage usage down.

    It's also possible we'd need to explicitly delete stuff in cleanup.

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Thu Dec 11 22:34:08 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/90ab818538ea2e7d66e498ef
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    Put the suppressions in sbbs-build archive

    Should fix valgrind jobs using empty.

    Also, add some debug stuff to the cleanup job

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Thu Dec 11 22:40:33 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/2ec1a34fc1122e251f90ad90
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    Use suppressions from sbbs-build archive

    We can't use the ones from git since it's not there anymore.

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Thu Dec 11 22:40:33 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/f24fdc057eb19f653c9a9312
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    Tweak debug output a bit in cleanup

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Thu Dec 11 23:05:01 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/ab068d5a2305c8db7669b01b
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    It's not CI_PROJECT_NAME, maybe CI_PROJECT_NAMESPACE?

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Thu Dec 11 23:27:59 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/4eadd3dc3f7e70ce5b812dff
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    Do some hackery to clean up

    For each job, touch ${CI_PIPELINE_ID}.ci at the start.
    During cleanup, remove all */${CI_PROJECT_NAMESPACE} directories
    that have ${CI_PIPELINE_ID}.ci in them.

    This should prevent build directories from having more than one
    namespace in them at the same time going forward

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Thu Dec 11 23:31:10 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/1212aaf3fa66fab6c4cebe0f
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    File created is ${CI_PROJECT_NAMESPACE}/${CI_PROJECT_NAME}/${CI_PIPELINE_ID}.ci

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Thu Dec 11 23:36:05 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/4387bea71f7abd3b8f942f69
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    Remove dupe

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Thu Dec 11 23:38:59 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/f39e705b00d8835e216256c3
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    Using empty strategy adds -empty to project name

    So don't use it... go back to none.

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Tue Dec 16 15:10:03 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/87941e04617ce255fc7b19f2
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    Don't clean up main.

    Leaving the checked-out sources there saves a lot of time.

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Thu Jan 1 18:11:59 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/5f6d0cd1d412ef6c752480b8
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    JSexec requires a successful config load, by default now

    So use (new) -U option to defeat that requirement when running tests

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Fri Jul 17 03:04:32 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/43cc4d49f3c0feb9a651d4ed
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    CI: fail the door test jobs when they run no tests at all

    ctest's default for an empty test set is to print "No tests were found!!!"
    and exit 0, so a test step that runs nothing passes. Both door jobs that
    run tests could do this, which makes the guard quietly conditional on
    wiring it cannot see: rename TERMGFX_TESTS or SYNCRETRO_TESTS, or let the
    -D stop taking effect, and ctest reports success having executed nothing.

    This is not hypothetical. The [termgfx] job ran ctest against a tree whose
    test target did not exist yet and was green for its first several
    pipelines, reporting a passing test step that had run zero tests -- the
    exact failure the step exists to catch, in the step meant to catch it.

    Pass --no-tests=error so an empty set is a failure (ctest exits 8). Both
    jobs already use --test-dir, added in the same CMake 3.20 as this flag, so
    it costs no new version floor. The [termgfx] job's ctest is spelled like syncretro's while here, rather than cd-ing into the build dir.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Fri Jul 17 21:23:33 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/d1946415d2583bd2fbe9d215
    Modified Files:
    .gitlab-ci-unix.yml
    Log Message:
    CI: run the xpdev mixer regression test in the test stage

    Add an [xpdev-test] test-stage job that builds xpdev and mixertest from
    source and runs "make test" (nonzero exit == failure), so the
    xp_mixer_pull gapless-drain fix cannot silently regress. It needs the
    [xpdev] build job for ordering and, where valgrind is available, runs the regression under the leak checker (--error-exitcode=1). Skipped on cross-compiled targets, whose foreign-arch binary the runner cannot run.

    Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net