On Wed, Feb 28, 2018 at 06:38:36PM +0000, Daniel P. Berrangé wrote:
The further down the workflow a problem is detected the more time
expensive
/ disruptive it is to fix it. So while having post-build tests to validate
lots of things is great (and I wish we had more of it in Fedora), I see it
as complementary to anything that we can do to detect problems earlier. I
rather see failures right away when I test the new RPM build locally, than
waiting to push it through koji and wait again for post-build tests to find
the problem, as by that time I've context switched my mind away to a
different bit of work.
Oh, I agree, but I think this is optimizing at the wrong end. Instead
of failing when you build, the new-upstream tracker should update your
RPM and do a test build as soon as new upstream is detected, so your
first interaction should be "Hey, there's a new version of this, and
when we tried to build it, there's files missing from the previous
version... can you take a look?"
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader