sean/builder-images
Watch
1
0
Fork
You've already forked builder-images
 0
Code Issues Pull requests Projects Releases 144 Packages Wiki Activity

docs: these images build natively, not on an Argo Workflow #236

Closed
sean wants to merge 1 commit from sean/native-build-path into trunk AGit
pull from: sean/native-build-path
merge into: sean:trunk
Conversation 0 Commits 1 Files changed 1 +8 -3
sean commented 2026-09-08 15:09:13 +00:00
Owner
Copy link

Three README claims went stale when builder-images moved to the native executor. The ci-builder-images-pipeline Argo Workflow lived in sean/pipelines, which deploys nothing; Binjovi now compiles a fanout graph of durable tasks and publishes each item as its own task. Two table rows said workers were 'for Binjovi Argo Workflows'; those projects all build natively. The binjovi-argocd-deployer row keeps 'Argo CD' unchanged -- Argo CD stays. This release is also the first exercise of ReleaseItemPublisher.Native end to end.

Three README claims went stale when builder-images moved to the native executor. The ci-builder-images-pipeline Argo Workflow lived in sean/pipelines, which deploys nothing; Binjovi now compiles a fanout graph of durable tasks and publishes each item as its own task. Two table rows said workers were 'for Binjovi Argo Workflows'; those projects all build natively. The binjovi-argocd-deployer row keeps 'Argo CD' unchanged -- Argo CD stays. This release is also the first exercise of ReleaseItemPublisher.Native end to end.
docs: these images build natively, not on an Argo Workflow
Some checks failed
binjovi/ci Binjovi failed the frozen plan
Details
df5f97d430
 
Three claims went stale when the project moved to the native executor.

"The ci-builder-images-pipeline Argo Workflow builds these images" is now
plainly false. That Workflow lived in sean/pipelines, which sources zero
ArgoCD Applications and zero Flux GitRepositories and deploys nothing.
Binjovi compiles the image set into a fanout graph of durable tasks the
build agents claim, and publishes each item as its own durable task.

Two table rows described workers as being "for Binjovi Argo Workflows".
Every project that uses them builds natively today. The
binjovi-argocd-deployer row keeps "Argo CD convergence observer" exactly
as it is: Argo CD stays, and 28 Applications depend on it. Only Argo
Workflows is being removed.

Claude-Session: https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76
sean closed this pull request 2026-09-09 13:18:38 +00:00
Some checks failed
binjovi/ci Binjovi failed the frozen plan
Required
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/builder-images!236
No description provided.