On 12/18/25 11:03, Cristian Le via devel wrote:
My concerns about missing zuul-feature parity in no particular order:
- ELN scratch builds were available in Zuul
There is a tracker for this [1]. I tried to find a project that is currently
enrolled to test the eln, but couldn't find one, and afaict there is support
in packit itself, so not quite sure what part is missing there. I pinged the
tracking issue to get an update on that.
Note that the linked issues is about CI on the eln branch. I don't know if
Zuul supported that, I don't have any projects with an eln branch.
What I had in mind is ELN scratch build for rawhide pull requests. The Zuul
jobs are called check-for-eln and eln-rpm-scratch-build.
This prevents accidentally braking the build for the %rhel/%fedora conditionals.
And it makes it easier for testing actual changes of some aspect of the build
wrt. such conditionals. However, in such case, I can submit a manual ELN
scratchbuild, so the previous point is more important to me.
Oh interesting, I missed that aspect. Hmm I am thinking if I could make it as a
tmt test since that would minimize the special code that packit would need to
carry. Would a mock build also work for that? Seems like we would need another
issue for this, would you open it in packit-service and we can check what
options we have?
I have opened https://github.com/packit/packit-service/issues/2920 and will
followup there.
--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
