WIKIMEDIA/PYWIKIBOT-CORE REPO WAS RENOMED TO WIKIMEDIA/PYWIKIBOT
AHHHH

AppVeyor is very weird in handling organizations. For now, this runs automatically from the github repo: https://ci.appveyor.com/project/Ladsgroup/pywikibot-g4xqx

Probably we could move Travis and AppVeyor builds to Jenkins after post-merge build? This would be somewhat better than relying on GitHub forks which can cause issues like this (when renaming a repository).

Hi, I notice this task has Diffusion-Repository-Administrators on it, but I'm not sure I understand how this is related to Diffusion? Is that site pulling from the Diffusion copy of the Pywikibot repo?

In T183860#4683099, @Krenair wrote:

Hi, I notice this task has Diffusion-Repository-Administrators on it, but I'm not sure I understand how this is related to Diffusion? Is that site pulling from the Diffusion copy of the Pywikibot repo?

I'm not sure, why I added RepoAds, sorry. The problem is that nobody has got an access to Wikimedia account on AppVeyor (which operates with GitHub mirror). There are two possible solutions:

• contact @jayvdb as he was the Wikimedia AppVeyor account founder
• move AppVeyor tests to Jenkins post-merge

No, we need your help!

In T183860#4683354, @Dvorapa wrote:

I'm not sure, why I added RepoAds, sorry. The problem is that nobody has got an access to Wikimedia account on AppVeyor (which operates with GitHub mirror). There are two possible solutions:

• contact @jayvdb as he was the Wikimedia AppVeyor account founder

That is the subject of T104306. I do not know AppVeyor at all, at least it uses GitHub with OAuth which simplify things a bit. Does it support organization somehow? Then we would be able to add pywikibot maintainers to it and you will be able to modify settings on a self served basis.

I am fine being added as an admin as well to help pywikibot people. On a best effort basis though, but I should be able to act when subscribed to tasks.

• move AppVeyor tests to Jenkins post-merge

What kind of tests are being run? We used to have a Jenkins job running some subset of tests against the beta cluster, but it did not ever worked properly. It is surely something we could revisit and should be as simple as defining a new tox environment (eg: smoketest-beta) which would have all the proper commands to initialize pywikibot, select tests and point them at https://en.wikipedia.beta.wmflabs.org/ . We should be able to have the job to report to IRC and by email and run it on a daily/hourly basis.

In T183860#4765323, @hashar wrote:

In T183860#4683354, @Dvorapa wrote:

I'm not sure, why I added RepoAds, sorry. The problem is that nobody has got an access to Wikimedia account on AppVeyor (which operates with GitHub mirror). There are two possible solutions:

• contact @jayvdb as he was the Wikimedia AppVeyor account founder

That is the subject of T104306. I do not know AppVeyor at all, at least it uses GitHub with OAuth which simplify things a bit. Does it support organization somehow? Then we would be able to add pywikibot maintainers to it and you will be able to modify settings on a self served basis.

I am fine being added as an admin as well to help pywikibot people. On a best effort basis though, but I should be able to act when subscribed to tasks.

In T104306#4765339, @hashar wrote:

There is some documentation at https://www.appveyor.com/docs/team-setup/ Seems the AppVeyor accounts/team can be tied to the GitHub ones.

@hashar Yeah, but first Wikimedia has to get access to the existing Wikimedia account on AppVeyor

• move AppVeyor tests to Jenkins post-merge

What kind of tests are being run? We used to have a Jenkins job running some subset of tests against the beta cluster, but it did not ever worked properly. It is surely something we could revisit and should be as simple as defining a new tox environment (eg: smoketest-beta) which would have all the proper commands to initialize pywikibot, select tests and point them at https://en.wikipedia.beta.wmflabs.org/ . We should be able to have the job to report to IRC and by email and run it on a daily/hourly basis.

CI build tests run on AppVeyor and Travis automatically on every commit merged. These include unittests, nosetests, pytests, doctests and several others (coverage by Codecov, complexity by Codeclimate...) on multiple environments: Python 2, 3.4, 3.5, 3.6, 3.7 (to be added soon) on Linux, Windows (not working yet) and Mac (not working yet). It would be cool to move these tests to jenkins post-merge as Wikimedia people promised us multiple times. But the current process (of using AppVeyor and Travis official web application) worked too. Just we have no access to the Pywikibot AppVeyor account.

There is a request open to install AppVeyor on some of the wikimedia github repositories. Is it supposed to be on non-pywikibot stuff like MW?

Change 860953 had a related patch set uploaded (by Xqt; author: Xqt):

[pywikibot/core@master] [doc] Update Appveyor link

https://gerrit.wikimedia.org/r/860953

Change 860953 merged by Xqt:

[pywikibot/core@master] [doc] Update Appveyor link

https://gerrit.wikimedia.org/r/860953