console
console copied to clipboard
[release-4.11] OCPBUGS-2077: Find latest pipeline run without firehose selector
Manual cherry pick of #12071
Conflict occured in PipelineAugmentRuns.tsx
@rottencandy: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh
.
In response to this:
[release-4.11] OCPBUGS-2063: Find latest pipeline run without firehose selector
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@rottencandy: This pull request references Jira Issue OCPBUGS-2063, which is invalid:
- expected Jira Issue OCPBUGS-2063 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found
Comment /jira refresh
to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
Manual cherry pick of #12071
Conflict occured in
PipelineAugmentRuns.tsx
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/jira refresh
/cc @vikram-raj
@rottencandy: This pull request references Jira Issue OCPBUGS-2063, which is invalid:
- bug is open, matching expected state (open)
- bug target version (4.11.z) matches configured target version for branch (4.11.z)
- bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
- bug has dependents
- dependent bug OCPBUGSM-43696 is not in the required
OCPBUGS
project
All dependent bugs must be part of the OCPBUGS project. If you are backporting a fix that was originally tracked in Bugzilla, follow these steps to handle the backport:
- Create a new bug in the OCPBUGS Jira project to match the original bugzilla bug. The important fields that should match are the title, description, target version, and status.
- Use the Jira UI to clone the Jira bug, then in the clone bug: a. Set the target version to the release you are cherrypicking to. b. Add an issue link “is blocked by”, which links to the original jira bug
- Use the cherrypick github command to create the cherrypicked PR. Once that new PR is created, retitle the PR and replace the BUG XXX: with OCPBUGS-XXX: to match the new Jira story.
Note that the mirrored bug in OCPBUGSM should not be involved in this process at all.
Comment /jira refresh
to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira refresh
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@rottencandy: This pull request references Jira Issue OCPBUGS-2077, which is invalid:
- expected dependent Jira Issue OCPBUGS-2063 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA instead
Comment /jira refresh
to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
Manual cherry pick of #12071
Conflict occured in
PipelineAugmentRuns.tsx
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@rottencandy: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh
.
In response to this:
[release-4.11] OCPBUGS-2077: Find latest pipeline run without firehose selector
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rottencandy, vikram-raj
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/packages/pipelines-plugin/OWNERS~~ [vikram-raj]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
/label backport-risk-assessed
/cc @sanketpathak /cc @hemantsaini-7
/jira refresh
@vikram-raj: This pull request references Jira Issue OCPBUGS-2077, which is valid. The bug has been moved to the POST state.
6 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.11.z) matches configured target version for branch (4.11.z)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
- dependent bug Jira Issue OCPBUGS-2063 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
- dependent Jira Issue OCPBUGS-2063 targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
- bug has dependents
Requesting review from QA contact: /cc @sanketpathak
In response to this:
/jira refresh
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/label cherry-pick-approved
/retest-required
@rottencandy: all tests passed!
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@rottencandy: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-2077 has been moved to the MODIFIED state.
In response to this:
Manual cherry pick of #12071
Conflict occured in
PipelineAugmentRuns.tsx
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/cherrypick release-4.10
@vikram-raj: new pull request created: #12265
In response to this:
/cherrypick release-4.10
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.