Hi, @loongci
AFAICT, There is no such kind of service, script, or command existing for rpm build so far.

IMO, the logic of this automation is straightforward, and it could be implemented like:
- Watch the tagging actions of your build tags
- Once "build B" is tagged into the build tag, check all builds which buildrequires "package B" (in your dist tag) by comparing with the nvrs in the build's buildroot, or parsing buildrequires and provides ("build C" should be there)
- If the creation of the build repo of "build C" is before the tagging action of "build B", rebuild "build C"

BTW, please report issues in English so that most developers are able to read. Although the translation softwares are much smarter than before, they may not understand the complex logic of programming.

Thanks

Chinese -> English translation of the issue content for others don't understand Chinese:

# How to determine the package dependencies to compile?
Assuming that there are 3 software packages A, B, and C, and the dependency order is A->B->C, I have made a bugfix in the B software, and B has been submitted successfully and the version has changed, how to let C automatically trigger compile? Is there any script or command? Please advise, thanks

Chinese -> English translation of the issue content for others don't understand Chinese:

How to determine the package dependencies to compile?

Assuming that there are 3 software packages A, B, and C, and the dependency order is A->B->C, I have made a bugfix in the B software, and B has been submitted successfully and the version has changed, how to let C automatically trigger compile? Is there any script or command? Please advise, thanks

Hi, @loongci
AFAICT, There is no such kind of service, script, or command existing for rpm build so far.

IMO, the logic of this automation is straightforward, and it could be implemented like:
- Watch the tagging actions of your build tags
- Once "build B" is tagged into the build tag, check all builds which buildrequires "package B" (in your dist tag) by comparing with the nvrs in the build's buildroot, or parsing buildrequires and provides ("build C" should be there)
- If the creation of the build repo of "build C" is before the tagging action of "build B", rebuild "build C"

BTW, please report issues in English so that most developers are able to read. Although the translation softwares are much smarter than before, they may not understand the complex logic of programming.

Thanks

When B is officially compiled to repo, will the C software be automatically compiled once?

When B is officially compiled to repo, will the C software be automatically compiled once?

No, it won't.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/3435

Please continue any further discussion there.