#22 Creating components in the tests/ namespace not working
Opened 4 years ago by hhorak. Modified 3 years ago

Handling tickets that request a new component in the tests/ namespace does not work.

Started by a ticket [1] created using fedpkg tool, and then trying to make things working with hand-made tickets [2], [3] -- none worked because the tooling handling the tickets expects fields only valid for RPMs.

Please, fix the tooling, so tickets created by fedpkg request-tests-repo (like [1]) are properly handled.

Thanks.

[1] https://pagure.io/releng/fedora-scm-requests/issue/19437
[2] https://pagure.io/releng/fedora-scm-requests/issue/19549
[3] https://pagure.io/releng/fedora-scm-requests/issue/19845


@pingou or @mprahl, which repo is the correct one to file a manual request for creating a component in the tests/ namespace? I don't see any reasonable repo under https://pagure.io/projects/releng/.

More cases of this issue:

https://pagure.io/fedora-infrastructure/issue/8755

I think fedscm-admin should not require a bug for tests creations.

Also branch is always master on test namespace right?

Finally monitoring makes no sense...

@kevin to the branch .. default is 'master'. People should be able to create new branches if needed though. Are there some limitations for that?

I've pushed PR #30 and another PR to fedpkg to try to fix this bug.

I have replaced Mattia's PR for fedpkg with this one if you are interested in.
https://pagure.io/fedpkg/pull-request/387

As there are no other comments nor confirmations at #387, I will merge this today.

Commit 5672d905 relates to this ticket

Currently in fedpkg-1.38-3.fc33 (rawhide). Other releases will follow after dependencies are resolved or updates are aproved.

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #388 Merged 4 years ago
  • #387 Merged 4 years ago
  • #30 Merged 3 years ago