-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
Re-Trigger PipelineRuns for a tag
-
False
-
-
False
-
In Progress
-
0% To Do, 50% In Progress, 50% Done
-
-
Epic Goal
Tekton+PaC@Konflux supports retriggering build pipelines for a specific non-default branch. https://konflux.pages.redhat.com/docs/users/building/rerunning.html#retriggering-a-post-merge-build-from-from-github
In addition to that, for ACS project, we need an ability to retrigger build pipelines for a specific tag. E.g. with a comment like /retest branch:refs/tags/3.21.1 or /retest tag:3.21.1.
Technically tag pushes and branch pushes are separate signals and there are important differences in our build process so that ability to retrigger builds for a branch is not sufficient.
- We'd like to be able to retrigger without re-pushing a tag.
- We also need to be able to retrigger when the tagged commit does not belong to any branch or is not the most recent commit on any branch.
For more details, please see this Slack thread: https://redhat-internal.slack.com/archives/C04PZ7H0VA8/p1743763030606959
Why is this important?
- …
Scenarios
- ...
Acceptance Criteria (Mandatory)
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- Acceptance criteria are met
- Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
- User Journey automation is delivered
- Support and SRE teams are provided with enough skills to support the feature in production environment
- duplicates
-
-
- Closed
-
- is blocked by
-
SRVKP-8701 Testing for the epic
-
- To Do
-
- is documented by
-
RHDEVDOCS-6781 Document re-triggering pipelines for a git tag support
-
- Open
-