Here it is: https://github.com/orf/django-github-actions/tree/master/.github/workflows <https://github.com/orf/django-github-actions/tree/master/.github/workflows>
There are two actions I’ve added here: a lint step and a matrix of sqlite tests (Windows, MacOS and Ubuntu * py36 and py37). It’s all vanilla Django on the latest master, however I did remove the pylibmc dependency for now as that’s slightly tricky to include (and there are no 3.8 wheels available). I’ve got four example PR’s for you: 1. Linting failures: https://github.com/orf/django-github-actions/pull/1 <https://github.com/orf/django-github-actions/pull/1> 2. A failing test: https://github.com/orf/django-github-actions/pull/2 <https://github.com/orf/django-github-actions/pull/2> 3. Nothing failing: https://github.com/orf/django-github-actions/pull/3 <https://github.com/orf/django-github-actions/pull/3> 4. Modifying the CI to test on Python 3.8: https://github.com/orf/django-github-actions/pull/4 <https://github.com/orf/django-github-actions/pull/4> I’ve had some experience with actions but all this took me about half an hour (on very poor airport WiFi). It’s really simple and really effective. The devil is obviously in the details but based on my work with docker-box we can make good progress with our test matrix really fast. And we can do it step-by-step. The usage limits are documented here: https://help.github.com/en/github/automating-your-workflow-with-github-actions/about-github-actions#usage-limits <https://help.github.com/en/github/automating-your-workflow-with-github-actions/about-github-actions#usage-limits>. I’m not sure how they apply to organisations (maybe just “free”?), but I think Github would allow us an increased limit. What do we think? Tom > On 6 Nov 2019, at 13:58, Tom Forbes <t...@tomforb.es> wrote: > > Yes there will be. Now Github has added caching I think we are good to go. > > I will send a link here with the longer running on my fork and we can look at > starting there. Once (if?) that’s merged then we can enable the “allow forks > to run actions” option and we can iteratively add more tests as merge > requests. > > Regarding Jenkins: it’s a beast that’s often unreliable. We save on effort > there, get a more reliable CI tool and have our CI files versioned alongside > our code. > > I’m not sure open vs closed source comes into play here, and it should be > mentioned that Github actions (the steps and the runner) is almost completely > open source. And believe me when I say the source is a lot easier to > follow/debug than the reams of often incomprehensible code a Jenkins plugin > typically has! > > Tom > >> On 6 Nov 2019, at 12:56, Preeti Sharma <preetidevs...@gmail.com> wrote: >> >> >> Right, but there has to be some changes done i think. >> >> On Wed 6 Nov, 2019, 6:05 PM Florian Apolloner, <f.apollo...@gmail.com >> <mailto:f.apollo...@gmail.com>> wrote: >> >> >> On Wednesday, November 6, 2019 at 8:43:21 AM UTC+1, Shai Berger wrote: >> Is there benefit enough in GitHub Actions (over Jenkins) to justify a >> move from an open-source based solution? >> >> Yes, less server costs (even if sponsored). Less things to maintain for us >> (Jenkins is a beast). Better and more reliable integration with github. >> >> -- >> 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 >> <mailto:django-developers+unsubscr...@googlegroups.com>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/d34795bc-7490-43b0-bdcb-8a3023939c9b%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/d34795bc-7490-43b0-bdcb-8a3023939c9b%40googlegroups.com?utm_medium=email&utm_source=footer>. >> >> -- >> 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 >> <mailto:django-developers+unsubscr...@googlegroups.com>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CAMzw02X%2BqLKO6hKKh6bT0JzVBUubeO4AaW4o3YQAXnCpxcJvYw%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/django-developers/CAMzw02X%2BqLKO6hKKh6bT0JzVBUubeO4AaW4o3YQAXnCpxcJvYw%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1BB1752C-4408-4B8F-9A3B-E7B502FA6E19%40tomforb.es.
