#336 Add c9 to SIG branches naming convention for CentOS Stream 9
Closed: Fixed a year ago by arrfab. Opened a year ago by amoralej.

Cloud SIG is doing some testing with CentOS Stream 9 published composes and we'd like to start pushing distgits content to c9-sig-cloud-<whatever> branches even if we still can't build in CBS for it. Would it be possible to add c9-sig-cloud to the branches names pattern where we can do git push?, i think we can only use c7 and c8 so far.


@bstinson : can we get your opinion on this ? Ideally we'd have this feature available once we also are able to import c9s tree as externalrepo into cbs.centos.org.
I personally don't mind already allowing SIGs to start pushing to sig-<name>-el9s* branches on git.centos.org but probably worth discussing the wider plan and communicate on centos-devel list too ?

Metadata Update from @arrfab:
- Issue tagged with: centos-common-infra, doc, feature-request, groomed

a year ago

For some context, we are doing some builds using mock and centos9 composes to start testing. I'd like to push to distgits to get ready for it and also to make sure we don't lose that work. Anyway if we need to wait, i can understand it.

The Hyperscale SIG is going to need this too fwiw

let me ask again is that's something we're allowed/authorized to do and once we have green light, we'll implement the small needed change in ansible

@bstinson any update on this request?

@bstinson @carlgeorge could we proceed with this as SIG prep for CS9 ?

Let's go ahead and allow c9s SIG branches

Following git commit was pushed (and applied by ansible):

* 8540a17 - (HEAD -> master, origin/master, origin/HEAD) Allowed c9s as valid SIG prefix for branches #336 (50 seconds ago) <Fabian Arrotin>

Can you verify that it works for you ?

Will c9s SIG branches be able to follow the same dist-git layout as the main c9s package repos?

Metadata Update from @arrfab:
- Issue unmarked as depending on: #324
- Issue assigned to arrfab

a year ago

@ngompa good question but based on initial discussion the plan was to still use the 'rpm-style' layout as that's the only one that centpkg-minimal (used in cbs/koji to rebuild the src.rpm at build time) knows and can handle.
Closing initial request as c9s prefix is now possible on git.c.o

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Following git commit was pushed (and applied by ansible):
* 8540a17 - (HEAD -> master, origin/master, origin/HEAD) Allowed c9s as valid SIG prefix for branches #336 (50 seconds ago) <Fabian Arrotin>

Can you verify that it works for you ?

Thanks @arrfab I confirm it works fine now.
$ git push origin c9s-sig-cloud-openstack-xena:c9s-sig-cloud-openstack-xena
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 241 bytes | 241.00 KiB/s, done.
Total 3 (delta 0), reused 2 (delta 0)
remote: - to mqtt
remote: ERROR: [u'git', u'rev-list', u'65272f5ee4df35ea232b8688f897500cbb08a079', u'^HEAD'] =-- 128
remote:
remote: fatal: bad revision '^HEAD'
remote:
remote: Sending to redis to send commit notification emails
To ssh://git.centos.org/rpms/python-ddt
* [new branch] c9s-sig-cloud-openstack-xena -> c9s-sig-cloud-openstack-xena

Login to comment on this ticket.

Metadata
Boards 1