jayvdb added a comment. In https://phabricator.wikimedia.org/T74863#1707770, @jayvdb wrote:
> Travis-CI has a similar functionality : > http://docs.travis-ci.com/user/uploading-artifacts/ > But it requires manually setting up an `AWS S3` account. They offer free > accounts, so I'm going to try that now to see how feasible it is. So, despite using their 'free' offering, I am billed AUD 0.11 for uploading a single build, consisting of 20 `.coverage` files. https://travis-ci.org/jayvdb/pywikibot-core/builds/84076536 Maybe I set this up wrong, but it seems too simple to be charged, so I dont think this is an appropriate solution. > Another approach is for the Travis script to push the coverage data to a > dedicated github repo, or even a gist, so that it is archived in case it is > needed. > For example we could create a repo called something like > `pywikibot/coverage-data` , and the push would work for any one who has > commit access to that repo. An environment variable could override that repo > identifier, for anyone who doesnt have commit access to that shared repo. So, maybe we do this? Any other approaches? anonymous dpaste? TASK DETAIL https://phabricator.wikimedia.org/T74863 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: jayvdb Cc: Ladsgroup, XZise, gerritbot, Aklapper, jayvdb, pywikibot-bugs-list _______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
