Remove the sqlite3 file handling from the pipeline

[adrpo]

Since #296 the results of a job go into the shared database. The old path — a per-machine sqlite3.db downloaded before the run and published back afterwards — was still there, chosen by a tick box on the job:

booleanParam(name: 'postgres', defaultValue: true, description: '... Untick to go back to the sqlite3 files.')

Nobody should be able to send a day of testing to a file nobody reads by unticking a box before a build, and keeping the old path around only leaves two ways of doing the same thing for someone to wonder about later. So it all goes:

• the postgres parameter and the branches it guarded;
• copying ~/TEST_LIBS_BACKUP/<machine>-sqlite3.db into the workspace before a run, copying it back after, and the sshPublisher that uploaded it;
• fetching a machine's sqlite3.db in the two report stages, which read the shared database directly;
• keeping a week of dated backups of those files on every node;
• dbPrefix and sshConfig, which existed only to name and publish that file, from runRegressiontest and its 23 callers.

The scripts are untouched. test.py and the report scripts still default to a local sqlite3.db, which is what a developer gets when running them by hand and what the GitHub checks use. It is the pipeline that no longer has a second way of doing this.

Checked

Removing two positional parameters from a function with 23 callers is the kind of edit that goes wrong quietly, so the calls were rewritten by parsing each argument list rather than by matching text, and then verified against the new signature:

signature (14): branch, name, extraFlags, omsHash, omcompiler, extrasimflags, testFlags,
                removePackageOrder, conversionScript, jobs, libs_config_file, cmakeFlags,
                dockerfile, fmiSimulators
required: 9, optional: 5
23 calls checked, 0 problems

The check confirms every call is within the arity the signature allows and that the argument now in the omcompiler position is a boolean in all of them. That last one caught a genuine mistake while writing this: the first attempt also rewrote the definition, silently dropping omcompiler and extrasimflags from the signature while every caller still passed them.

---

Generated by Claude Code.