Skip to content

Conversation

iblancasa
Copy link
Contributor

@iblancasa iblancasa commented Oct 2, 2024

Version(s): 4.18, 4.17, 4.16, 4.15, 4.14, 4.13, 4.12

Issue: TRACING-4615

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Signed-off-by: Israel Blancas <iblancas@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 2, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 2, 2024

@iblancasa: This pull request references TRACING-4615 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.18.0" version, but no target version was set.

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 2, 2024
Copy link

openshift-ci bot commented Oct 2, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 2, 2024
@iblancasa iblancasa marked this pull request as ready for review December 3, 2024 12:06
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 3, 2024

@iblancasa: This pull request references TRACING-4615 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.19.0" version, but no target version was set.

In response to this:

Version(s): 4.18, 4.17, 4.16, 4.15, 4.14, 4.13, 4.12

Issue: TRACING-4615

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 3, 2024
@ocpdocs-previewbot
Copy link

Copy link

openshift-ci bot commented Dec 3, 2024

@iblancasa: 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-sigs/prow repository. I understand the commands that are listed here.

@iblancasa iblancasa closed this Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants