Better isolate builds #86
Labels
No Label
Roadmap
V
bug
docs
duplicate
enhancement
good first issue
help wanted
idea
invalid
question
wontfix
Idea
Roadmap
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#90 Add logs for builds
vieter-v/vieter
Reference: vieter-v/vieter#86
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
The current system makes it so that all builds are ran one by one inside the same Docker container. While this makes things more practical (we only have to update the repositories once), it also makes it possible for packages to contaminate each other's dependencies, or cause a package to mistakingely think its PKGBUILD correctly lists a dependency.
One idea would be to use clean chroots, but it seems these aren't as straightforward to setup inside Docker.
This idea could be combined with a way to configure a max number of concurrent builds, which could be useful to speed up builds.
Idea: run all the mutual commands (updating repos, create build user, etc.) first, then create an image with a unique (maybe based on time & date) name. This image could then be used by all packages to build. This would prevent having to update the repos for each package, while still keeping their builds isolated.