Pin the MEOS source to a committed MobilityDB commit - #241
Merged
estebanzimanyi merged 1 commit intoJul 31, 2026
Merged
Conversation
The MEOS vcpkg port builds MobilityDB from a fixed commit SHA instead of resolving master's tip at configure time. A moving ref changes the libmeos source on every push, which defeats the extension pipeline's ccache (it keys on source content): libmeos and its dependencies recompile from scratch every CI run. A pinned ref keeps the source stable, so ccache reuses the libmeos objects and each build after the first collapses to a link — cutting the per-PR build from tens of minutes. The committed generated UDF surface already comes from this same commit, so libmeos and the surface that links against it stay matched. Advancing the tracked MobilityDB version is a deliberate bump of this SHA together with a surface regeneration from it, which the daily surface-refresh workflow can drive.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Speeds up CI and stops the generated-surface drift by building MEOS from a fixed commit SHA instead of resolving
mastertip at configure time.Why it speeds up builds: the extension pipeline caches
ccache(keyed on source content). A moving master ref changes the libmeos source on every push, so libmeos and its heavy deps recompile from scratch each run. A pinned ref keeps the source identical, so ccache reuses the libmeos objects and each build after the first collapses to a link — cutting the per-PR Linux build from ~15–20 min toward ~5–8 min.Why it stops the drift cascade: the committed generated UDF surface already comes from this same commit, so libmeos and the surface that links against it stay matched — no more per-merge regen/rebase churn as master moves.
The pin is set to the SHA the current committed surface is generated from, so this changes nothing about what libmeos is built (guaranteed compatible) — it only makes the source stable. Advancing the tracked MobilityDB version is a deliberate bump of this SHA together with a surface regeneration, which the daily surface-refresh workflow can drive.