merge feat/deploy-gate-eventsource (8aee500c10) #216

Open
pipeline-bot wants to merge 1 commit from feat/deploy-gate-eventsource into trunk
Collaborator
No description provided.
Deploys now trigger on the pipeline-release resource EventSource when the
project's PipelineRelease reaches status.deployable==true, instead of on a git
main-push (which advances mid-release and raced deploys ahead of green).
status.deployable latches true only when the WorkflowProjector sees the release
Workflow Succeed, so a deploy can no longer start before its release is green.

- sensorSpec gains EventSourceName/EventName/FilterFields/DeterministicName,
  defaulted so every build/staging/autoland sensor renders byte-identically.
- argocd/flux/ibmi deploy profiles: dependency release-deployable, filter
  project==<p> && deployable=='true', sha from body.spec.sha, deterministic
  <project>-deploy-<sha12> name (dedups the EventSource's repeat status fires),
  drop the body.before->fromSha injection (fromSha='' is cosmetic-only).
- goldens (pipelines/seanfarm/rpg-hello) + parity reference sensor-deploy.yaml
  regenerated; non-deploy sensors unchanged.
All checks were successful
pipeline/ci CI green v0.1.46
Required
Details
This pull request has changes conflicting with the target branch.
  • CHANGELOG.md
  • internal/render/sensors.go
  • internal/render/testdata/golden/pipelines.yaml
  • internal/render/testdata/golden/rpg-hello.yaml
  • internal/render/testdata/golden/seanfarm.yaml
  • internal/render/testdata/reference/pipelines/sensor-deploy.yaml
  • internal/render/testdata/reference/rpg-hello/sensor-deploy.yaml
  • internal/render/testdata/reference/seanfarm/sensor-deploy.yaml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/deploy-gate-eventsource:feat/deploy-gate-eventsource
git switch feat/deploy-gate-eventsource
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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/pipelines-operator!216
No description provided.