#32566 closed Cleanup/optimization (invalid)
Earthly for builds?
| Reported by: | Vlad A. Ionescu | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 3.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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!
Change History (2)
comment:1 by , 3 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 3 years ago
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.
Note:
See TracTickets
for help on using tickets.
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.