1. Forum
  2. DOVE-Net
  3. Synchronet Programming

  • .gitlab-ci.yml

    From Deucе@VERT to Git commit to main/sbbs/master on Sun Dec 7 09:20:53 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/252ad9e2df46111e3f0cc861
    Modified Files:
    .gitlab-ci.yml
    Log Message:
    Since the RPi 500 is so fast, enable GTK and valgrind as well

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Mon Jan 26 19:25:37 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/f2a3a7a9074855f2dbc40f44
    Modified Files:
    .gitlab-ci.yml
    Log Message:
    Limit the MSBuild to 2 parallel builds

    to hopefully fix, once and for all, the occasional and unpredictable
    'fatal error C1001: Internal compiler error.' during CI.

    This is going to slow down the windows-x86 build (of sbbs3 solution).

    ---
    þ 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 Wed Feb 25 18:43:30 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/d9854928b0d1ef9e270b3855
    Modified Files:
    .gitlab-ci.yml
    Log Message:
    Move the MSBuild core/thread limit to the correct command-line

    Whoops, maybe *this* will help eliminate the occassional msvc cl.exe crashes.

    ---
    þ 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 Wed Feb 25 20:45:10 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/d4e06a54b02d7171437ae532
    Modified Files:
    .gitlab-ci.yml
    Log Message:
    Let's try one core/thread for sbbs3 msvc build

    We still got "Internal compiler error" with 2

    ---
    þ 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 Sun Mar 1 05:49:02 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/361f40d857068bf8ed7ef729
    Modified Files:
    .gitlab-ci.yml
    Log Message:
    Remove the CPU/thread limit - it didn't stop the MSVC internal compiler error

    ---
    þ 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 Jul 16 19:28:45 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/f2e799d47b37a435a0cd6df6
    Modified Files:
    .gitlab-ci.yml
    Log Message:
    CI: run a pipeline when the CI definition itself changes

    The .rules changes: list covered the sources a build consumes -- src/,
    3rdp/, ctrl/text.dat, exec/tests/ and the makefile globs -- but not the pipeline definition. A commit touching only .gitlab-ci.yml or .gitlab-ci-unix.yml therefore matched no rule and created no pipeline at
    all, so a CI change could not test itself: it sat unvalidated until some
    later commit happened to touch src/ or 3rdp/, which is exactly when a
    mistake in it is most surprising.

    The commit that added the termgfx door jobs hit this: it changed only the
    two CI files, so nothing ran, and the jobs it defined stayed unproven.

    Match .gitlab-ci*.yml so such a commit runs the pipeline it edits. The
    glob covers both the top-level file and the included per-platform one.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Fri Jul 24 23:17:57 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/1edeb70972df50b128638ce1
    Modified Files:
    .gitlab-ci.yml
    Log Message:
    CI: build the Win32 doors

    Nothing covered the doors' MSVC builds, so three of the eight had been
    broken for a while with no pipeline to say so (128a6b52d9). One job per
    door that has an MSVC build -- the same set src\doors\build.bat calls
    buildable on Windows -- which also gives syncrpg and syncscumm their
    first CI job on any platform.

    Modelled on the .<os>-termgfx-door jobs: each door is driven through its
    own build.bat, the documented entry point that encodes its CMake flags,
    and needs nothing from the library jobs since these trees build xpdev,
    termgfx and their vendored engine as sub-targets. The Clans is the
    exception with no build.bat of its own, so it goes through the umbrella
    script, which already carries the MSBuild probe.

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

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