bd808 added a comment.
In T399415#10999020 <https://phabricator.wikimedia.org/T399415#10999020>, @Xqt wrote: > In T399415#10998648 <https://phabricator.wikimedia.org/T399415#10998648>, @bd808 wrote: > >> I guess my first question is if these tests could run from Wikimedia infrastructure rather than GitHub Actions. > > We could probably use **self-hosted runners** on WMF infrastructure: > > - https://docs.github.com/en/actions/how-tos/hosting-your-own-runners > - https://docs.github.com/en/actions/concepts/runners/about-self-hosted-runners > - https://docs.github.com/en/actions/how-tos/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners > - https://docs.github.com/en/actions/concepts/runners/communicating-with-self-hosted-runners > > But I am not able to set it up I guess but I am willing to support as much as I can if this is an appropriate solution. Background: Previously we had these tests at Travis and Appveyer. Both text matrix were ported to github action due to T296371 <https://phabricator.wikimedia.org/T296371> and T368192 <https://phabricator.wikimedia.org/T368192>. These tests after Jenkins CI uses a wider variance of sites, Python releases, OS and tests users (Jenkins tests is for en-wiki and IP user only) and helps to verify that the code is ready to be published as a next stable release if tests passes. There are 128 jobs running <https://github.com/wikimedia/pywikibot/actions/metrics/performance> on github. > > To port these tests to Jenkins looks much more difficult to me and I have no idea if and how this would be possible. > >> The fundamental challenge today is that we only have IP range based blocking setup for the Beta Cluster without any currently documented way to bypass a range block by using a request header/authentication/etc. > > I found out that tests needs five times as much time running on beta than before or on other sites (if we were lucky that the runner's IP is not blocked) and I understand the measure. But it is cumbersome to restart the failing jobs every time in the hope of reaching an unblocked IP. Blocking IP cannot be a long-term solution and you also have to ask yourself what to to if other sites than beta are affected. So there should be any bypass mechanism for trusted CI traffic through headers or tokens or maxlagish throttling. But you know that better than I do. TASK DETAIL https://phabricator.wikimedia.org/T399485 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/
_______________________________________________ pywikibot-bugs mailing list -- pywikibot-bugs@lists.wikimedia.org To unsubscribe send an email to pywikibot-bugs-le...@lists.wikimedia.org
