On 29/07/2019 11:31, Pierre-Yves Chibon wrote:
On Mon, Jul 29, 2019 at 11:23:32AM +0100, Tom Hughes wrote:
> On 29/07/2019 11:08, Pierre-Yves Chibon wrote:
>> On Fri, Jul 26, 2019 at 02:19:18PM +0100, Tom Hughes wrote:
>>> On 26/07/2019 14:17, Tom Hughes wrote:
>>>> On 23/07/2019 21:51, Pierre-Yves Chibon wrote:
>>>>
>>>>> This is the first roll-out of this gating change, and so there may
>>>>> be additional
>>>>> tuning and fixes until things are as smooth as we want them to be.
>>>>> With this
>>>>> release we are looking for feedback on what can be improved. We have
>>>>> a dedicated
>>>>> team working on this project and we will be taking your feedback
>>>>> into account to
>>>>> improve the experience.
>>>>
>>>> Not getting five additional emails for every rawhide build I do
>>>> would probably be a good start?
>>>
>>> Correction, make that seven, as I hadn't gotten to the ones
>>> sent by notifications (as opposed to bodhi) yet...
>>
>> So only counting the ones from bodhi, how many would be acceptable?
>> 2? update was created, update was pushed to the buildroot?
>> Or do we want just one: "update was pushed to the buildroot"?
>
> Well this was a package that didn't have CI enabled at all
> so it's not clear any of them are very useful.
The update was pushed to the buildroot seems useful as it means things are
working the way they should, but I guess koji wait-repo --build does the same if
you're relying on it.
Well koji wait-repo is also more reliable, as the bodhi message
fires as soon as it is submitted while wait-repo tells you when
the compose has completed and the package is available to use.
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/