Sorry for bumping such an old thread, but I've created a github actions POC and written it up here: https://forum.djangoproject.com/t/improving-the-contribution-experience-with-github-actions/5964
On Monday, 11 November 2019 at 08:11:57 UTC Johannes Maron wrote: > Hi Mariusz, > > Cool, let me know if you have any questions about the config file that I > wrote. I am happy to help :) > > Regarding the output, yes I can feel you. However I don’t know if we > really need to run tests at verbosity level 2 on CI. One can always do that > online or enable it if need be. > > At list of tests that failed in a human readable output format would be > nice. GitHub supports annotation on checks, but it's not really convenient > yet to be used. > > Using it for linters is a good start. We could also do the docs build and > limit that one to be only build if the docs actually changed. You can > trigger builds based on file condition > <https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths>, > > which is pretty neat. > > Something that we also haven’t explored are scheduled builds. Those could > be helpful to do regression tests on especially on dependencies. > > Anyhow, love to see where this is going. > -Joe > On 11. Nov 2019, 15:53 +0900, Mariusz Felisiak <felisiak...@gmail.com>, > wrote: > > > I would suggest to open a PR to GitHub now and to get the Fellows >> involved. Ask them how to best integrate a trial without disturbing their >> workflow. What do you guys think? >> >> > I'm going to play with GitHub actions in this week (or in the next one) > but I'm still not convinced. It's fine to use them for linters, but for > more complicated jobs it generates output that is less readable, IMO. You > don't get a formatted table but a raw output, so you have to scroll down > ~20k lines to check what went wrong. This can be really frustrating > especially with more then one failure. Nevertheless I'm going to play with > it. > > Best > Mariusz > > > -- > 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/xDCmZPLTOQQ/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > django-develop...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/6692d50f-b02d-4824-aa12-be22a20c3f0f%40googlegroups.com > > <https://groups.google.com/d/msgid/django-developers/6692d50f-b02d-4824-aa12-be22a20c3f0f%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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0c944a34-6c73-457b-a860-a8b355589113n%40googlegroups.com.
