Bug 2023303

Summary:	How to add custom CI jobs to Centos9 composes gating
Product:	Red Hat Enterprise Linux 9	Reporter:	Alfredo Moralejo <amoralej>
Component:	distribution	Assignee:	RHEL Program Management <pm-rhel>
Status:	CLOSED MIGRATED	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	alex.iribarren, apevec, bstinson, jwboyer
Target Milestone:	rc	Keywords:	MigratedToJIRA, Reopened
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-14 11:20:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alfredo Moralejo 2021-11-15 12:01:06 UTC

Opening this question from Cloud SIG as a bz as requested from https://pagure.io/centos-infra/issue/513

In different talks from CentOS Stream, it has been mentioned a future mechanism to add custom jobs to composes gating CI. For SIGs, that'd be very useful as a way to provide early feedback on potential issues with centos updates even if those jobs are only for reporting purposes and not blocking composes promotion.

In my case, i'd be interested in running OpenStack jobs to validate we keep working with newer composes.

The purpose of this ticket is to track the status of this work in centos infra, if there is already a mechanism to implement this or if there are plants to provide one.

Comment 2 RHEL Program Management 2023-05-15 07:28:47 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 3 Alfredo Moralejo 2023-05-30 09:16:58 UTC

reopenning after being auto-closed by RHEL rules. I'd like to get proper feedback about this request.

Comment 5 RHEL Program Management 2023-09-14 11:18:50 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-14 11:20:35 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.