On Mon, 29 Apr 2019 at 08:11, Neal Gompa <[email protected]> wrote: > On Mon, Apr 29, 2019 at 7:51 AM Stephen John Smoogen <[email protected]> > wrote: > > > > > > > > On Mon, 29 Apr 2019 at 07:35, Neal Gompa <[email protected]> wrote: > >> > >> On Mon, Apr 29, 2019 at 7:21 AM Kamil Páral <[email protected]> > wrote: > >> > > >> > > On Wed, Apr 24, 2019 at 12:19 AM Kevin Fenzi <kevin(a)scrye.com> > wrote: > >> > > > >> > > > >> > > It will be nice but I am not aware of any other system in place > which would > >> > > replace checks performed by autocloud. > >> > > > >> > > (CC'ed tflink and kparal) > >> > > Does taskotron provides capability to perform tests on Fedora cloud > Images > >> > > like booting images and other basic checks? > >> > > >> > (My email to the list was rejected because I'm not subscribed, let me > try again from the web UI...) > >> > > >> > Theoretically it is possible using nested virt. However, Taskotron is > going away as well. The replacement is Fedora CI: > >> > https://docs.fedoraproject.org/en-US/ci/ > >> > > >> > >> But Fedora CI is broken and/or vaporware. How can we replace Taskotron > >> with that? > >> > > > > Honestly.. weren't we saying the same damn thing about taskotron until > Fedora CI became the latest thing to rail about. It was constantly 'why do > you spend time on this broken crap' and then it becomes the 'oh why are you > replacing my favorite thing in the world'. I am pretty sure there are > multiple thesis and doctorates on the codependency that OpenSource > developers exhibit.. > > > > > > I actually don't remember this for Taskotron... I'm pretty sure that's > because most of us can't interact with it. > > The problem with Fedora CI is that it's documentation is useless and > attempts to use the system end in miserable failure. > > What I'm annoyed about is the continual replacement of things with > stuff that works _less_ than before. I'm sure this has a lot to do > with "agile" and pushing "minimal viable products" as full > replacements, with the hope that it'd iteratively build up. That > doesn't seem to happen quickly enough for things to be useful, and > sometimes the effort going in falls off before it reaches parity with > what it replaced. > > As much as I would love to blame Agile/MVP as much as the next guy... part of the reason things keep getting replaced versus worked on is what the developers here from the community is 'X is completely broken, either get rid of it or I am gone.' That and the fact that most developer thinks whatever they (or someone else) wrote last week is complete dog-vomit, leads to a constant iteration of replacement tools. 2-3 years ago it was a weekly email flood of 'Fedora build systems suck.. they have no CI and you can't do CD'
Look this is remodeling the house. It is very hard to make the master bedroom bigger when we are also told not to make the rooms around it smaller. It is even harder when you have to do it while the people live in the house and we aren't allowed to wake or bother anyone while we do all this work. So you are going to end up with Tata's because anything bigger can't fit in the Civic. > Replacing a Honda Civic with a Tata Nano just doesn't fly. > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > _______________________________________________ > infrastructure mailing list -- [email protected] > To unsubscribe send an email to > [email protected] > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/[email protected] > -- Stephen J Smoogen.
_______________________________________________ infrastructure mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
