BuildXL
earthly-solutions
| BuildXL | earthly-solutions | |
|---|---|---|
| 2 | 1 | |
| 890 | 3 | |
| 1.1% | - | |
| 0.0 | 7.9 | |
| 4 days ago | 6 months ago | |
| C# | TypeScript | |
| MIT License | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
BuildXL
-
We built the fastest CI in the world. It failed
Seems they came up with a way to scale up build toolchains with BuildXL[0]
Doesn't seem fully baked yet though
[0]: https://github.com/microsoft/BuildXL
-
Using Landlock to Sandbox GNU Make
> With regards to chroot, I stand corrected. I knew it was a tree of symlinks, but I thought it was also more than that because symlinks alone don't seem like a sandbox. Honestly, Cosmopolitan's system appears to be more of a sandbox than that.
To be totally clear: the tree of symlinks thing is a fallback, used only when lacking platform support or when sandboxing is explicitly turned off [0]. On Linux, the normal sandboxing strategy is to use namespaces, like most container runtimes. On Mac it apparently uses sandbox-exec (some opaque Apple tool), as was mentioned above. Chroot, being both non-POSIX, requiring root access on many systems, and not providing the necessary facilities is not really a great fit -- which I assume is why it's not used.
There was experimental Windows sandbox support at one point [1] based on how MS does it for BuildXL (their own build tool for giant monorepos) [2]. Unfortunately it doesn't seem to be maintained, and under the hood it's kinda ugly -- it actively rewrites code in-memory to intercept calls to the Win32 APIs [3], which was apparently the cleanest/best way MS could come up with. However, from Bazel's POV it works in a roughly similar way -- you spawn subprocesses under a supervisor, which is in charge of spinning up whatever the target process is with restrictions on time/memory usage/file access.
On the "sandbox in the interpreter" thing: what kind of checks are you envisioning? It seems like putting checks at that level would end up leaving a lot out -- the goal of any build system is to eventually spawn an arbitrary process (Python, gcc, javac, some shell script, etc.) and so even with extensive checks in starlark you'd end up with accidental sandbox breaks all over the place. For pure starlark rules you could e.g. check that there are no inputs from /usr, but even then if gcc does it implicitly, you're SOL. Or am I thinking of the wrong kind of checks?
[0] https://bazel.build/docs/sandboxing#sandboxing-strategies
[1] https://github.com/bazelbuild/bazel/issues/5136#issuecomment...
[2] https://github.com/microsoft/BuildXL/blob/master/Documentati...
[3] https://github.com/microsoft/Detours/wiki
earthly-solutions
-
We built the fastest CI in the world. It failed
https://github.com/earthly/earthly-solutions
What are some alternatives?
Microsoft Research Detours Package - Detours is a software package for monitoring and instrumenting API calls on Windows. It is distributed in source code form.
act - Run your GitHub Actions locally 🚀
wireit - Wireit upgrades your npm/pnpm/yarn scripts to make them smarter and more efficient.
bass - a low fidelity scripting language for project infrastructure
Concourse - Concourse is a container-based continuous thing-doer written in Go.
Bazel - a fast, scalable, multi-language and extensible build system
sso-wall-of-shame - A list of vendors that treat single sign-on as a luxury feature, not a core security requirement.
make-audit - Easy-to-use tool for auditing Makefiles for errors
pmaudit - "Poor Man's Audit" (lightweight build-auditing script)
Sidekiq - Simple, efficient background processing for Ruby