On 29. 04. 19 14:32, Pierre-Yves Chibon wrote:
On Mon, Apr 29, 2019 at 08:22:31AM -0400, Neal Gompa wrote:
On Mon, Apr 29, 2019 at 8:21 AM Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote:
On Mon, Apr 29, 2019 at 08:10:59AM -0400, Neal Gompa wrote:
On Mon, Apr 29, 2019 at 7:51 AM Stephen John Smoogen <smooge@xxxxxxxxx> wrote:
On Mon, 29 Apr 2019 at 07:35, Neal Gompa <ngompa13@xxxxxxxxx> wrote:
On Mon, Apr 29, 2019 at 7:21 AM Kamil Páral <kparal@xxxxxxxxxxxxxxxxx> 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.
Sorry for asking, but could you point me to the tickets you've opened for the
issues you've seen/faced?
I personally haven't opened any tickets because I can't figure out how
to use it. But I've heard from others (Fabio, Miro, etc.) that none of
it works, so I haven't bothered trying to dig into it anymore.
Would be nice to rely on your own experience rather than hearsay :)
I'm not saying Miro hasn't had problems, he has said so in a few occasions
before with links to tickets he opened but I'm hearing a lot of people
bad-mouthing CI while there aren't so many tickets on:
https://pagure.io/fedora-ci/general/ considering how wide it is deployed and
should impact the community.
So I'm questioning if people are bad-mouthing because they've heard other people
doing it or because they have legitimate issues that have been reported and
should be fixed.
I'm very happy to help raise concerns/issues from the community about issues
about the CI pipeline but I need to have hard-facts and tickets to be able to do
so, not hear-say.
I am opening tickets a there is nothing by silence.
The CI people are glad to help me solve immediate problems (figure out why it
errored this time again), but for long term issues, there is nothing.
My personal favorites:
There is no way to see what's going on:
https://pagure.io/fedora-ci/general/issue/2 (8 months old)
There is no way to reproduce+debug easily:
https://pagure.io/fedora-ci/general/issue/4 (8 months old)
There is no way to see why it errored:
https://pagure.io/fedora-ci/general/issue/43 (1 month old)
There is no way to see when it errored:
https://pagure.io/fedora-ci/general/issue/49 (fresh)
There is no way to rely on CI not erroring by random reason:
https://pagure.io/fedora-ci/general/issue/44 (1 month old)
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
