ci(frontend): build pinned commit on master push via Pipelines-as-Code - #1164
Merged
Merged
Conversation
TwoDCube
force-pushed
the
pac-build-trigger
branch
from
June 6, 2026 16:38
7e8ea5d to
4208768
Compare
TwoDCube
changed the title
TwoDCube
force-pushed
the
pac-build-trigger
branch
from
June 6, 2026 17:11
4208768 to
93e15c7
Compare
On a push to master, Pipelines-as-Code runs the maintained openshift-client task, which creates a self-contained Shipwright BuildRun (embedded build.spec pinned to the pushed commit) and `oc wait`s for it, reporting the result back as a GitHub check. No standalone Build CR and no polling loop are required.
TwoDCube
force-pushed
the
pac-build-trigger
branch
from
June 6, 2026 17:25
93e15c7 to
2b79d44
Compare
TwoDCube
changed the title
Member
|
/lgtm |
Member
Author
|
/approve |
TwoDCube
added
the
approved
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smrtrfszm, TwoDCube The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
2 participants
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.
What
Adds
.tekton/push.yamlso every push tomasterrebuilds the frontend image, pinned to the exact pushed commit.How it works
On a push to
master, Pipelines-as-Code runs thisPipelineRunin theverseghynamespace. Its single task references the cluster's maintainedopenshift-clienttask (via theclusterresolver — no hand-rolled taskSpec/image), whoseSCRIPT:oc creates a self-contained ShipwrightBuildRun— the full build recipe lives inline inspec.build.spec, withsource.git.revisionpinned to the pushed SHA (a BuildRun referencing a Build by name can't override the revision);oc wait --for=jsonpath='{.status.completionTime}'blocks until the build finishes — this returns on success or failure, so there's no polling loop;Succeededcondition and exits non-zero on failure, so the result lands on the commit as a GitHub check.Runs as the
pipelineSA (hascreate/get buildrunsviaClusterRole/edit).Companion PR
Verseghy/website_k8s#28 — removes the now-unreferenced standaloneBuildCRs and keeps only the PACRepositorybindings.Validation
yqparse,prettier --check, server-side dry-run of thePipelineRunand the generatedBuildRun, and a live throwaway PipelineRun confirming theclusterresolver +pipelineSA executeocsuccessfully — all green against the live cluster.