releng

#8938 Please create f31-coreos-continuous tag
Closed: Fixed by mohanboddu. Opened by jlebon.

Closed: Fixed
Reopen Issue

With a setup similar to the f29-coreos-continuous tag and f30-coreos-continuous tag. Notably, with tag2distrepo enabled.

Thanks!

My understanding from before was that the -coreos-continuous tags would be automatically created at the same time all the other versioned tags are created. Is that not the case?

CoreOS tags are not created during branching. If you believe they should be, open PR and add tag creation to scripts/branching/make-koji-release-tags

Thanks for the pointer. Opened https://pagure.io/releng/pull-request/8939.

Though I suspect even with #8939 merged, we'll still need manual intervention to create the f31 and f32 ones, right?

The steps should be to update the PR:

$ koji add-tag f31-coreos-continuous --arches='x86_64 aarch64 ppc64le s390x'
$ koji add-target f31-coreos-continuous f31-build f31-coreos-continuous
$ koji edit-tag -x tag2distrepo.enabled=true f31-coreos-continuous

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

I see you've created the f31 tag. As mentioned in https://pagure.io/releng/issue/8938#comment-607129, I think we need the f32 version too, no? Since that script was run for branching f32 already.

Done.

$ koji add-tag f32-coreos-continuous --arches='x86_64 aarch64 ppc64le s390x'
$ koji add-target f32-coreos-continuous f32-build f32-coreos-continuous
$ koji edit-tag -x tag2distrepo.enabled=true f32-coreos-continuous
Metadata
None
None
None
None
None
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.