[Django] #32566: Earthly for builds?

8 views
Skip to first unread message

Django

unread,
Mar 17, 2021, 2:26:30 PM3/17/21
to django-...@googlegroups.com
#32566: Earthly for builds?
------------------------------------------------+------------------------
Reporter: vladaionescu | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Uncategorized | Version: 3.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Hi there,

I'm wondering if you're interested in trying out Earthly
([https://github.com/earthly/earthly]) for builds.

Earthly could help with reproducing CI failures locally (via containers)
and testing against multiple versions of Python in parallel, or against
multiple DBs in isolated integration tests.

It works well on top of Travis.

Happy to put together a demo PR if this is of interest. Let me know!

--
Ticket URL: <https://code.djangoproject.com/ticket/32566>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Mar 17, 2021, 3:18:39 PM3/17/21
to django-...@googlegroups.com
#32566: Earthly for builds?
-------------------------------------+-------------------------------------
Reporter: Vlad A. Ionescu | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Uncategorized | Version: 3.1
Severity: Normal | Resolution: invalid

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Nick Pope):

* status: new => closed
* resolution: => invalid


Comment:

Please don't use this bug tracker for spamming your advertising products
you work on.

If you think that your product would be beneficial, you could bring it up
on the DevelopersMailingList.

However, I expect that it'll be a hard sell, and if it were accepted,
you'd likely be asked to make a significant contribution to the effort.

As an aside, I note that you talk of it working well on top of Travis,
which clearly shows you've not looked into how Django's CI is implemented.
We currently use Jenkins and have been slowly migrating pieces to GitHub
Actions.

--
Ticket URL: <https://code.djangoproject.com/ticket/32566#comment:1>

Django

unread,
Mar 17, 2021, 3:38:05 PM3/17/21
to django-...@googlegroups.com
#32566: Earthly for builds?
-------------------------------------+-------------------------------------
Reporter: Vlad A. Ionescu | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Uncategorized | Version: 3.1
Severity: Normal | Resolution: invalid

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Vlad A. Ionescu):

Sounds good, thank you for the pointers. I don't mind a significant
contribution effort if it's beneficial.

Got my wires crossed re Travis. But yeah, it works well on top of Jenkins
& GH Actions too.

--
Ticket URL: <https://code.djangoproject.com/ticket/32566#comment:2>

Reply all
Reply to author
Forward
0 new messages