Add speculative build support: auto-detect and source staging - #91
Draft
rebtoor wants to merge 1 commit into
Draft
Add speculative build support: auto-detect and source staging#91rebtoor wants to merge 1 commit into
rebtoor wants to merge 1 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
rebtoor
force-pushed
the
feature/content-provider-speculative
branch
from
August 18, 2026 08:12
14823b1 to
77dfb5b
Compare
rebtoor
changed the title
rebtoor
force-pushed
the
feature/content-provider-speculative
branch
from
August 18, 2026 08:21
77dfb5b to
fd37ed7
Compare
|
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
Contributor
Author
|
recheck |
rebtoor
force-pushed
the
feature/content-provider-speculative
branch
from
August 18, 2026 08:55
fd37ed7 to
7ecf7e8
Compare
This was referenced Aug 18, 2026
rebtoor
force-pushed
the
feature/content-provider-speculative
branch
5 times, most recently
from
August 18, 2026 13:41
36e58a3 to
9e3951d
Compare
Enable the s2i content provider to automatically determine which images to build based on the triggering Zuul project, and to stage patched source checkouts from the Zuul workspace into container build contexts. This is a lightweight alternative to the OIB Python package from PR openstack-k8s-operators#49, implementing only the two features needed for RHOSRFE-466 (speculative testing of upstream OpenStack changes): 1. `build.sh auto-detect <project> [stream]` — scans sources.txt files to find which container images reference a given upstream project. Uses exact URL-path matching to avoid false positives (e.g., openstack/watcher does not match openstack/watcher-tempest-plugin). 2. Ansible playbooks for Zuul integration: - resolve-auto-images.yaml: resolves `s2i_ci_images: auto` by running auto-detect for each changed project in the Zuul queue. - stage-zuul-sources.yaml: copies Zuul-checked-out source repos into container src/ directories for speculative builds. Related-Issue: RHOSRFE-466 Co-Authored-By: Sean Mooney <work@seanmooney.info> Assisted-By: Claude (Anthropic) Co-authored-by: Cursor <cursoragent@cursor.com>
rebtoor
force-pushed
the
feature/content-provider-speculative
branch
from
August 18, 2026 13:42
9e3951d to
aac5d56
Compare
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.
Summary
build.sh auto-detect <project> [stream]command that scanssources.txtfiles to determine which container images are affected by a given upstream OpenStack project.resolve-auto-images.yaml) and source staging (stage-zuul-sources.yaml).sources.txtfiles).This is a lightweight alternative to the OIB Python package from PR #49, implementing only the two features required for speculative testing of upstream OpenStack changes (RHOSRFE-466):
openstack/tempest), determine which images need rebuilding by parsingsources.txtmanifests. Uses exact URL-path matching to avoid false positives.src/directories so builds use the speculative code instead of pinned hashes.How it works
When the content provider runs with
s2i_ci_images: auto:resolve-auto-images.yamlinspects the Zuul queue to find which external projects triggered the build.build.sh auto-detectto find affected images.stage-zuul-sources.yamlcopies Zuul's patched checkouts into the container build contexts.Note
This PR includes the content provider infrastructure from PR #85 and is intended to supersede it once validated.