Can you elaborate please ?

I quote @bookwar from matrix

https://pagure.io/centos-infra/issue/1278#comment-874950 so i indeed said "no rpms" when I first requested a sig infra. And we need a new ticket there to get access to cbs properly. I think we should request a build_integration tag for a SIG. I would not create a separate tag for packit for now as we don't have other rpms to build anyway, so there is no risk in mixing this package with official packages

I am working on this card related with this epic.

@mmassari : please still elaborate on what you want/need :)

If you request a new build target (and corresponding tags), please ensure to follow the official guide : https://sigs.centos.org/guide/cbs/ and then we can proceed.
Also need a +1 from sig chair ( /cc: @bookwar )

@arrfab thanks for your patience. I am new to the CentOS world, I read multiple times the official guide you suggested me, before opening this issue, still I am missing something I can't see 😅

I would say I need a new build target (and corresponding tags) but I can't understand what I am missing in this request.
In the guide I read the following:

New build target¶
To request a new build target, open an infra ticket. Your request should also include the external repositories your target may need to be added (e.g epel, epel-next...).

Am I missing to list the external repositories for my package?
If so, we don't really need to ship our testing package. On the contrary, we want only to be able to submit a Koji build for it.
Does it explain what is missing?

so you don't want to build and distribute packages, but just build something in cbs (not in copr) ?
Based on https://sigs.centos.org/guide/cbs/#koji-naming-convention, we still need info
CentOS Stream 9 or 10 ?
Assuming you want just to test automation for centos stream 9 , what about something like :
integration9s-packages-test ?
That would mean that members of the sig-integration group would be able to submit build against integration9s-packages-test-el9s build target (but nothing would ever be tagged to -testing nor -release (and so nothing signed) and so nothing going to mirrors network.

Is that a good summary of what you're trying to achieve ?

Yes, your summary is perfect and also the target build you have suggested: integration9s-packages-test.
I would say we can start with CentOS Stream 9 and if needed I will ask later for the CentOS Stream 10 target.
It is good for us if anyone in the SIG Integration group is able to trigger a build in CBS Koji for our package.
And it is a good thing if our package does not reach any mirror, at least for the moment.

Thanks again for your help.

Created :

* Checking distribution el9s configuration...
 -> Checking integration config...
Creating user : integration
Using default options for integration/packages
Creating tag  : integration9s-packages-test-candidate
Creating tag  : integration9s-packages-test-testing
Creating tag  : integration9s-packages-test-release
 -> creating integration9s-packages-test-el9s
Added external repo centos9s-baseos to tag integration9s-packages-test-el9s-build (priority 5)
Added external repo centos9s-appstream to tag integration9s-packages-test-el9s-build (priority 10)
Added external repo centos9s-crb to tag integration9s-packages-test-el9s-build (priority 15)

FWIW, I just went with arch x86_64 as nothing was specified and it seems it's just there to test automation against cbs/koji and not real builds
Build target is so integration9s-packages-test-el9s

Perfect, we start with this. Thanks a lot!