Skip to content

26.9: Fetch LIMS product manifest, matched on version (Kanban #2052) - #197

Merged
labkey-willm merged 2 commits into
release26.9-SNAPSHOTfrom
26.9_fb_lims_manifest_version_match_2052
Sep 1, 2026
Merged

26.9: Fetch LIMS product manifest, matched on version (Kanban #2052)#197
labkey-willm merged 2 commits into
release26.9-SNAPSHOTfrom
26.9_fb_lims_manifest_version_match_2052

Conversation

@labkey-willm

Copy link
Copy Markdown
Contributor

Rationale

Backports the fetch-manifest mechanism (#195) and its major.minor version fix (#196) to release26.9-SNAPSHOT together, since this branch never had #195 at all. Needed once distributions#614 (the #613 backport to 26.9) lands and publishes manifests for this branch's LabKey version.

Related Pull Requests

Changes

… builds

Only runs under TeamCity (this is a public repo) or with FETCH_LIMS_MANIFEST=1 for local testing, and no-ops for any LABKEY_DISTRIBUTION with no manifest published, since it lists the product's S3 prefix rather than assuming one exists. Overwrites startup/manifest.properties, which previously carried no real content (just the LABKEY_STARTUP_DISTRIBUTION_EXTRA envsubst placeholder).
…sion (Kanban #2052)

fetch-manifest listed the whole product prefix and assumed exactly one manifest lived there. That broke once develop bumped 26.9->26.10 and both versions' manifests coexisted in S3 - old manifests stay (deleting them would break reproducing an older install), so the lookup now filters to the manifest matching LABKEY_VERSION's leading major.minor.
@labkey-willm
labkey-willm merged commit 1203c34 into release26.9-SNAPSHOT Sep 1, 2026
8 checks passed
@labkey-willm
labkey-willm deleted the 26.9_fb_lims_manifest_version_match_2052 branch September 1, 2026 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants