Upgrade GitHub Actions workflow - #157
Conversation
|
I believe we do require openssl to release a version. |
|
The reason we pull from git is to get the latest. 17.9 is not the latest. We can cache the build though |
|
Sorry Dave. I have to admit I didn’t pay much attention to the release process. I focused mainly on the builds in this initial PR to get some early feedback. I’ll review how the current release process works and come back with a revised PR. |
- Use prebuilt PostgreSQL x64 binaries instead of building from source - Build only the x86 libpq client library from source (NOT the full server) No official prebuilt x86 PostgreSQL binaries exist since PG 11. The test server is always x64; x86 libpq is only needed to compile and link the x86 ODBC driver. SSL is not required for the x86 client lib (CI tests use localhost). - Eliminate Win32/Win64 OpenSSL, pkgconfiglite dependencies (winflexbison is still required by the PostgreSQL meson build system) - Run standard and mimalloc builds in parallel using matrix strategy - Separate release job that runs only on version tags Closes postgresql-interfaces#156
|
@davecramer I've updated the PR to address both of your concerns. Please feel free to share any additional questions or suggestions. What changed:
What's kept from the original PR:
What's new:
Workflow structure: Timing (cached run on my fork):
On a cold run (no cache), |
|
Just confirmed that the release still works, thanks so much for this |
Closes #156
Key improvements:
meson compile ... libpq:shared_library. The test server is always x64; x86 libpq is only needed to compile/link the x86 ODBC driver. No SSL needed since CI tests use localhost.Results (first run, no caches):
Subsequent cached runs will be even faster since the x86 libpq, x64 binaries, and all tools are cached.