ART-14031: Look at Konflux first when searching for RPMs in images

[adobes1]

When asked a question related to RPMs in an image, release or a stream, art-bot will now first look through BigQuery for Konflux builds, and only if it doesn't find anything will it fall back looking at Brew build records.

Mainly affects the following queries:

• Which rpms are in <release>
• Where in <X.Y> is the <rpm or package name> package/rpm used
• What kernel is used in <release>

Requires openshift-eng/art-tools#2074

[openshift-ci-robot]

@adobes1: This pull request references ART-14031 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 story to target the "4.21.0" version, but no target version was set.

Details

In response to this:

When asked a question relating to RPMs in an image, release or a stream, art-bot will now first look through BigQuery for Konflux builds, and only if it doesn't find anything will it fall back looking at Brew build records.

Mainly affects the following queries:

• Which rpms are in <release>
• Where in <X.Y> is the <rpm or package name> package/rpm used
• What kernel is used in <release>

Requires openshift-eng/art-tools#2074

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]

@adobes1: This pull request references ART-14031 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 story to target the "4.21.0" version, but no target version was set.

Details

In response to this:

When asked a question related to RPMs in an image, release or a stream, art-bot will now first look through BigQuery for Konflux builds, and only if it doesn't find anything will it fall back looking at Brew build records.

Mainly affects the following queries:

• Which rpms are in <release>
• Where in <X.Y> is the <rpm or package name> package/rpm used
• What kernel is used in <release>

Requires openshift-eng/art-tools#2074

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.

[locriandev]

This could be improved with something like

if components:
    so.snippet(payload='\n'.join(sorted(components)),
    ...
else:  # no RPMs are used in the build
    so.say(f'build {nvr} does not include any RPM')

[adobes1]

Thank you, addressed in 1215292

[openshift-ci]

@adobes1: 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/security	1215292	link	false	/test security

Full PR test history. Your PR dashboard.

Details

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.

[locriandev]

/lgtm

[joepvd]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joepvd

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [joepvd]

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