I have some really good news! I managed to almost map our entire Jenkins suite to GitHub actions, except Oracle. Check out the output of the entire suite here.
And the config here: .github/workflows/ci.yml Furthermore, I followed Tom’s great advice and switched everything to services. The execution time is perfectly fine. The only exception is PostGIS, for the lack of an official container. It works good though, no an issue for me personally. 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? On 9. Nov 2019, 17:31 +0900, Tom Forbes <t...@tomforb.es>, wrote: > No there isn’t. Right now Docker-box is optimized for local development and > exists outside of the main repository, and for now I’d suggest not trying to > integrate it. That can be some future work though! > > Regarding services vs apt, docker services is the only realistic way to do > it. We cannot rely on all versions of every database we run to be packaged, > installable and configurable in Ubuntu in a timely + simple manner, and it > will quickly become a mess (different configurations between different > versions for example). > > Just supplying a matrix of database versions that pull and start stock > database images via “services” is simple and effective. This is basically how > docker-box works. Postgis is annoying, but we publish a docker image as part > of docker-box that we can use. > > Tom > > > On 9 Nov 2019, at 08:40, Johannes Hoppe <i...@johanneshoppe.com> wrote: > > > > > Then why not use all the work already done in django-docker-box there? > > >Then this would be "Run Django CI with Docker in the Azure cloud via > > >Github Actions instead of Jenkins via the Jenkins-Github integration > > >(plugin?)” > > > > @Matematica that sounds promising is there a PR for that, that I have > > missed? I’d love to not reinvent the wheel :) > > On 9. Nov 2019, 07:21 +0900, django-developers@googlegroups.com, wrote: > > > > > > Then why not use all the work already done in django-docker-box there? > > > Then this would be "Run Django CI with Docker in the Azure cloud via > > > Github Actions instead of Jenkins via the Jenkins-Github integration > > > (plugin?)" > > -- > > 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/fdcbfc00-977c-4587-a823-8e806cddf280%40Spark. > -- > 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-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/17BD40A2-6A1B-4B44-8F49-11F2520F9898%40tomforb.es. -- 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/5a5f99aa-53d7-4669-bc29-e411aab7ac46%40Spark.
