PR#978: get_next_release should check also running builds -

koji

#978 get_next_release should check also running builds

Merged Aug 16, 2018 by mikem. Opened Jun 21, 2018 by tkopecek.

tkopecek/koji issue977 into master

tkopecek commented Jun 21, 2018

Fixes: https://pagure.io/koji/issue/977

mikem commented Aug 14, 2018

We're passing the new option everywhere except initMavenBuild. Couldn't the same issue also affect maven builds in principle? I wonder if we shouldn't just leave the option off and make this the new behavior.

Can we imagine any potential problems from including state=BUILDING builds in the calculation?

rebased onto 58a9a8f7cdb19c9bebe2b55a2114a0cf0c208816

Aug 15, 2018

tkopecek commented Aug 15, 2018

I'm in. I just tried to do minimal change possible. But I agree, that it would be consistent across artifacts.

mikem commented Aug 16, 2018

Commit d1be3c23 fixes this pull-request

Pull-Request has been merged by mikem

Aug 16, 2018

Metadata

Assignee

None

Tags

No Tags

koji

#978 get_next_release should check also running builds Merged Aug 16, 2018 by mikem. Opened Jun 21, 2018 by tkopecek. tkopecek/koji issue977 into master

Metadata

#978 get_next_release should check also running builds

Merged Aug 16, 2018 by mikem. Opened Jun 21, 2018 by tkopecek.

tkopecek/koji issue977 into master