I realized I'm virtually always pushing commits in order to have a new build. I must admit that I'm also not aware of the purpose of fedpkg push when there's good old git push.
fedpkg push
git push
Currently, I'm most often using:
{{{ fedpkg push & fedpkg build }}}
I would instead prefer a single command way:
{{{ fedpkg build --push }}}
This basically lets me choose between a number of actions I'm running:
{{{ fedpkg build --scratch fedpkg build --scratch --srpm fedpkg build --push }}}
In my opinion, the goal of the action is to '''create a build''', therefore I suggest improving fedpkg build and the action just differ in which type of build I want to get and which other actions must be performed to achieve that.
fedpkg build
See also:
https://fedoraproject.org/wiki/User:Pavlix#Bump_a_rawhide_package_to_a_newer_version
IMHO this should be done server-side. There should be some service that listens on the fedmsg bus for dist-git push events and kicks off a new Koji build for each push. This would follow the convention of other modern CI systems.
There might be a problem if doing in server-side, that is how to disable that if packagers just want to push.
Metadata Update from @cqi: - Issue close_status updated to: None
Metadata Update from @cqi: - Assignee reset - Issue set to the milestone: 1.58 - Issue tagged with: RFE
This issue has been unresolved for more than a year, and is going to be closed within a week if no further action is taken. If you feel this is in error, please contact me. This is a cleaning process suggested by Jay Greguske. Copy of this ticket was already closed in JIRA tracker.
Metadata Update from @onosek: - Issue set to the milestone: None (was: 1.58)