Skip to content

Conversation

agullon
Copy link
Contributor

@agullon agullon commented Feb 19, 2025

Add script to generate a report for any OCP version with advisory, cves and jira tickets info. The report will be use to decide if new MicroShift advisory publication should be requested.

…cide if new MicroShift advisory publication should be requested
@agullon agullon changed the title add script to generate a advisory, cves and jira tickets report USHIFT-5377: add script to generate a advisory, cves and jira tickets report Feb 19, 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 Feb 19, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 19, 2025

@agullon: This pull request references USHIFT-5377 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.19.0" version, but no target version was set.

In response to this:

Add script to generate a report for any OCP version with advisory, cves and jira tickets info. The report will be use to decide if new MicroShift advisory publication should be requested.

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 requested review from jerpeter1 and pmtk February 19, 2025 11:44
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 19, 2025
@agullon
Copy link
Contributor Author

agullon commented Feb 19, 2025

/retest-required

@agullon
Copy link
Contributor Author

agullon commented Feb 19, 2025

/retest-required

@agullon
Copy link
Contributor Author

agullon commented Feb 27, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Feb 27, 2025

/retest-required

@jogeo
Copy link
Contributor

jogeo commented Mar 4, 2025

/lgtm

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

openshift-ci bot commented Mar 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, jogeo

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:

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

Copy link
Contributor

openshift-ci bot commented Mar 4, 2025

@agullon: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit d48e5bf into openshift:main Mar 4, 2025
9 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants