fedora-infrastructure

#7752 Tracker to make https://pagure.io/dusty/failed-composes/ official
Closed: Duplicate by kevin. Opened by mohanboddu.

Closed: Duplicate
Reopen Issue

The plan is move the code to releng project and run it under infra maintained instance, openshift, loopabull or anything else.

suggestions for project name? we need a repo where the code will live and one for where the issues get reported. My suggestion:

  • releng/failed-composes - issue gets file here
  • releng/failed-composes-code - source code

Metadata Update from @bowlofeggs:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: request-for-resources

suggestions for project name? we need a repo where the code will live and one for where the issues get reported. My suggestion:

releng/failed-composes - issue gets file here
releng/failed-composes-code - source code

Why cant they reside on the same repo? I prefer releng/failed-composes

suggestions for project name? we need a repo where the code will live and one for where the issues get reported. My suggestion:

releng/failed-composes - issue gets file here
releng/failed-composes-code - source code

After discussing with @dustymabe I am thinking of

releng/failed-composes - to file the compose failure issues
releng/compose-tracker - to host the source code

@kevin Any thoughts?
Edited by mohanboddu

Sounds good to me. Can I create the repos?

Sounds good to me. Can I create the repos?

Sure.

repos were created:

  • https://pagure.io/releng/failed-composes
  • https://pagure.io/releng/compose-tracker/

Can we just close this in favor of the RFR in 7770 ?

Metadata Update from @kevin:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)
Metadata
None

request-for-resources

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.