On Sat, Mar 7, 2020 at 1:05 AM Miro Hrončok <mhron...@redhat.com> wrote:
> On 07. 03. 20 0:29, Tim Flink wrote: > > If you have any questions about this, feel free to reply to this thread. > > Hello Tim. > > I have 3 questions. > I'll selectively pick just the questions I want to reply to and leave the rest to Tim :-) > > 1) On what level of Fedora leadership was this decision made (and where > can I > read about it)? > > 2) Why are we removing something that arguably has a lot of value with > something > that doesn't exist yet? > It's not a direct response to your question, but one important fact is that our beefy machines in Fedora Infrastructure are out of warranty now (and replacing them would cost a lot of money, I assume). That's one of the major reasons why they won't be migrated to the new datacenter location, I believe. > 3) And to get a bit more specific: How do we rewrite our general Python > versions > checks [1] to the Jenkins thing and how do we deploy them? (Our point of > contact > for this was previously Kamil Páral -- but I suppose that changes now, > correct?) > AFAIK, here's an example of a generic test support in tmt: https://github.com/psss/tmt/pull/96/files This just defines the environment and workflow. The actual command is inside the "--script 'some command'" part (in your case something like "--script 'python3 python_versions_check.py foobar-1.2-1.fc31'") , which is provided by the dispatcher (something like taskotron-trigger). The dispatcher part is not ready yet, but will be ready (reportedly) before Flock. So then you'll write some dispatcher integration code that will generate the correct command for your check. You can run it already without the dispatcher integration (by providing the --script command locally, i.e. running it on your own machine), but that's just for testing purposes, of course. This needs to get finished, polished, documentation created, examples shown, etc. It's not ready yet (and if I'm talking nonsense, someone please correct me). This should all fall under Fedora CI, as far as I know, so they should be the point of contact: https://docs.fedoraproject.org/en-US/ci/ > Thanks for running Taskotron so far. It helped us a lot in the past with > the > Python 2 to 3 transition. > I'm glad it had a positive impact in some areas. 👋
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
