Petr Pisar wrote:
> Technically you can make multiple builds from the very same branch and
> commit. And some of the builds can pass and some fail.
But only one of those will be the CI build used to make the decision.
So all that is needed is to ensure that we cannot have a non-CI build that
succeeds if the CI build fails. If fedpkg build is made as smart as I
suggest (mark the CI build as production instead of triggering a new build),
that will happen automatically anyway. Otherwise (or I suppose it could be
done as a sanity check either way), I suppose non-CI builds need to be put
on hold and only allowed to start if and when the CI build succeeded.
> In reality there are modules which refer a component by a release branch
> (e.g. "master" or "f33" branch).
If modules are piggybacking on the non-modular branches, they also need to
be treated as above: any module build for a not yet CIed commit needs to be
put on hold and only allowed to start if and when the CI build succeeded.
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
