Skip to content

Conversation

@machine424
Copy link
Contributor

@machine424 machine424 commented Nov 17, 2025

that exposes utf-8 metrics

the 0.5.0 tag is to be created: DONE https://github.com/rhobs/prometheus-example-app/releases/tag/v0.5.0

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

that exposes utf-8 metrics

the 0.5.0 tag is to be created
@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 Nov 17, 2025
@openshift-ci openshift-ci bot requested review from rexagod and slashpai November 17, 2025 20:32
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 17, 2025
@machine424
Copy link
Contributor Author

@simonpasquier, ok if I cut a 0.5.0 from https://github.com/rhobs/prometheus-example-app?
I'd like to validate openshift/prometheus#281 with it before merging it.

@machine424
Copy link
Contributor Author

/testwith ci/prow/e2e-agnostic-operator openshift/prometheus#281

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2025

@machine424, testwith: Error processing request. ERROR:

could not determine job runs: requested job is invalid. needs to be formatted like: <org>/<repo>/<branch>/<variant?>/<job>. instead it was: ci/prow/e2e-agnostic-operator

@machine424
Copy link
Contributor Author

/testwith openshift/cluster-monitoring-operator/main/e2e-agnostic-operator openshift/prometheus#281

2 similar comments
@machine424
Copy link
Contributor Author

/testwith openshift/cluster-monitoring-operator/main/e2e-agnostic-operator openshift/prometheus#281

@machine424
Copy link
Contributor Author

/testwith openshift/cluster-monitoring-operator/main/e2e-agnostic-operator openshift/prometheus#281

@juzhao
Copy link
Contributor

juzhao commented Nov 24, 2025

/testwith openshift/cluster-monitoring-operator/main/e2e-agnostic-operator openshift/prometheus#281

@machine424 machine424 changed the title WIP: chore: update ghcr.io/rhobs/prometheus-example-app to 0.5.0 MON-4424: update ghcr.io/rhobs/prometheus-example-app to 0.5.0 Nov 26, 2025
@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 Nov 26, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 26, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 26, 2025

@machine424: This pull request references MON-4424 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 task to target the "4.21.0" version, but no target version was set.

In response to this:

that exposes utf-8 metrics

the 0.5.0 tag is to be created

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

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-robot
Copy link
Contributor

openshift-ci-robot commented Nov 26, 2025

@machine424: This pull request references MON-4424 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 task to target the "4.21.0" version, but no target version was set.

In response to this:

that exposes utf-8 metrics

the 0.5.0 tag is to be created: DONE https://github.com/rhobs/prometheus-example-app/releases/tag/v0.5.0

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

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.

@machine424
Copy link
Contributor Author

/jira

@juzhao
Copy link
Contributor

juzhao commented Nov 26, 2025

/verified by existing tests

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 26, 2025
@openshift-ci-robot
Copy link
Contributor

@juzhao: This PR has been marked as verified by existing tests.

In response to this:

/verified by existing tests

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.

@juzhao
Copy link
Contributor

juzhao commented Nov 26, 2025

/retest-required

@machine424
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 26, 2025

@machine424: This pull request references MON-4424 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 task to target the "4.21.0" version, but no target version was set.

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

Copy link
Member

@slashpai slashpai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 26, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 26, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: machine424, slashpai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [machine424,slashpai]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 26, 2025

@machine424: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/versions d09423b link false /test versions

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.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD dcad825 and 2 for PR HEAD d09423b in total

@openshift-merge-bot openshift-merge-bot bot merged commit 508b445 into openshift:main Nov 26, 2025
20 of 21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants