Thanks Josh, I'll take a look at that. Also, I got past the pylibmc problem (I wasn't running `apt-get update` before attempting to install libmemcached-dev).
On Thu, Jul 12, 2018 at 8:58 AM Josh Smeaton <josh.smea...@gmail.com> wrote: > Hi Matt, > > The django-box project[0] uses very close to the same ansible > configuration that is used to configure all of the Jenkins slaves Django > uses with the notable omission of an Oracle builder. > > Since the repos are separate, there has been some divergence on the > Jenkins side of things, but nothing too major. If you find anything missing > I'd be happy to update the box repo. > > [0] https://github.com/django/django-box > > Regards, > > On Thursday, 12 July 2018 22:37:29 UTC+10, Matt Cooper wrote: >> >> Hi Carlton, thanks for your quick reply! >> >> I'm setting things up here >> <https://mattc-demo.visualstudio.com/python-ci-testing/python-ci-testing%20Team/_build?definitionId=8&_a=summary>. >> Let me know if you can't access that link. It's configured as a public >> project, meaning you shouldn't need a login to view it. (There are still >> some known issues with public projects -- we're in preview right now.) The >> build definition is actually specified here >> <https://github.com/vtbassmatt/django/blob/ci/.vsts-ci.yml> in my clone >> of the Django repo as a YAML file. We do offer grids (we call it "matrix") >> as well -- for testing purposes I'm only running against Python 3.5 on >> Linux but it's straightforward to add ranges. I would very much appreciate >> your guidance when and if you have the time. >> >> I'm confident we can put something together in terms of resources for the >> DSF. I want to first convince myself that we're credible technically -- if >> we have big gaps, no amount of dollars or build minutes from Microsoft >> would make it worth moving. Is it alright with you if we postpone further >> discussion on this topic? >> >> Sorry for the length -- what follows are just some specifics of what I've >> done so far. We can take this off-list if it gets too noisy. >> >> My build steps are essentially what you suggested. First, I make sure >> pip, setuptools, and wheel are up to date. Then I grab >> unittest-xml-reporting, install the rest of the py3.txt requirements, cd >> into tests, then ./runtests.py against a custom settings file (see below). >> >> One of the things I'm unclear on is where you get your settings files for >> configurations other than SQLite. The Jenkins build hints at copying over >> some directories for the other DBs, which I'm assuming have the settings >> and maybe fixtures. The non-SQLite databases are an area I need to think >> more about, so I'm not blocking the rest of my work on that. >> >> Other minor issues I've hacked around for now: >> >> - pylibmc wouldn't build for me (but I just got some advice from a >> colleague on troubleshooting that) so I've temporarily removed it. >> - I need to add a custom test runner ( >> xmlrunner.extra.djangotestrunner.XMLTestRunner), so I copied >> test_sqlite.py and make a 1-line addition. >> - tests.timezones.ForcedTimeZoneDatabase generates output with an >> invalid timestamp, so I have to delete that test's results or else the >> whole test reporting step fails. I'm not clear if the bug is on our side >> in >> VSTS or someplace in one of the XUnit implementations. >> >> >> I'm curious what issues you faced building GitHub repos. We've had >> support for several years, but greatly improved it over the last year. From >> an open source perspective, the worst problem the "black box" nature -- the >> community couldn't see built results, test failures, etc since VSTS >> projects were always private. Now with public projects, we're hoping to >> close that gap. >> >> Regards, >> Matt >> >> On Thu, Jul 12, 2018 at 3:17 AM Carlton Gibson <carlton...@gmail.com> >> wrote: >> >>> Hi Matt, >>> >>> The Jenkins configuration is not public I'm afraid. >>> >>> I'm one of the Django Fellows. If you wanted to invite me to your VSTS >>> project I would be happy to review and offer pointers as you did the actual >>> work, assuming that would help? >>> >>> The main thing would be setting up the grid of supported versions, >>> against different Pythons and DBs. I guess I'd start just with Python 3.7 >>> (or 3.6) using SQLite and then grow out from there. >>> >>> The most basic setup would just be: >>> >>> * Clone >>> * install pip dependencies >>> * cd tests && ./runtests.py. >>> >>> If you can set up the grid of supported environments, that becomes >>> interesting. >>> >>> I can only presume it's being actively worked on but, VSTS' integration >>> with GitHub wasn't great last time I looked (?) >>> >>> Finally, I don't think we're looking to move the CI but would Microsoft >>> provide free resource to the DSF (us) for testing Django? >>> >>> Thanks. Interesting. >>> >>> Kind Regards, >>> >>> Carlton >>> >>> >>> On Thursday, 12 July 2018 00:09:19 UTC+2, Matt Cooper wrote: >>>> >>>> Hi Django devs. I've looked all over for the tools that power >>>> djangoci.com, but I don't see them. Are the Jenkins configuration, >>>> scripts, and resources available someplace? >>>> >>>> Full disclosure, I'm on the Visual Studio Team Services group at >>>> Microsoft. We're making sure that our CI system is as good a home for >>>> Python (and PHP, and Ruby, and ...) projects as any system out there. One >>>> of the research activities I'm doing is trying to get a CI pipeline set up >>>> for well-known Python projects. Then I can see where we have gaps, where we >>>> have better features, etc. >>>> >>>> Thanks, >>>> Matt >>>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/django-developers/oDgv_Ztgd4s/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> django-develop...@googlegroups.com. >>> To post to this group, send email to django-d...@googlegroups.com. >>> Visit this group at https://groups.google.com/group/django-developers. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/3f25427c-2a96-4b30-a3a8-0987a4ecab61%40googlegroups.com >>> <https://groups.google.com/d/msgid/django-developers/3f25427c-2a96-4b30-a3a8-0987a4ecab61%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-developers/oDgv_Ztgd4s/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/79d082e1-b6b6-410a-8856-2886895d7549%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/79d082e1-b6b6-410a-8856-2886895d7549%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAGtApQUw%2Brz%2BDG2nULK1RzXF5xe0UC9mF8YSD0YU%2BiqEzeGgkg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
