scripts-to-rule-them-all
Buck
scripts-to-rule-them-all | Buck | |
---|---|---|
8 | 14 | |
3,140 | 8,564 | |
- | - | |
0.0 | 3.9 | |
over 1 year ago | 6 months ago | |
Shell | Java | |
Creative Commons Zero v1.0 Universal | Apache 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.
scripts-to-rule-them-all
-
What’s with DevOps engineers using `make` of all things?
Personally I like https://github.blog/2015-06-30-scripts-to-rule-them-all/ as a pattern and then let the authors do whatever crazy thing they want from there. In my experience, 99% of repos never move past using simple shell scripts with a few common functions with that pattern, and things are kept fairly simple. A select few repositories tend to mature enough that they are able to invest in swapping towards something more testable than shell scripts, and then you just have a couple people who stick to invoking `make` from the scripts but it's fine and nobody has to think about it except them. We don't stick to that exact set of scripts, but find that as long as you don't use more than like 10ish entrypoints in `script/*`, and have at least `script/bootstrap` it's fine.
- Scripts to Rule Them All (2015)
-
Just: A Command Runner
I dig the general idea, but question the value add over a directory of `scripts` that follow sane conventions (ie `script/test`, `script/build` etc). Is the main thing that you can do `just -l` to see available commands? I have never really reached for `make` when I've had a choice, as I've done mostly ruby, JS, or java where you have more sane, humane tools (i.e. Rake, Yarn, Maven though that one is never fun).
My general approach is every repo should have something that follows https://github.com/github/scripts-to-rule-them-all, written in sh (maybe bash, its 2023), linted with shellcheck. When you need something fancy Rake is great or grab some nice bash command line helper and source it from all your scripts. Is a command listing really worth another dependency over what you get from `ls script` or `cat script/README` ?
- [AskJS] What is the best way to create a common npm package for building others?
-
Azure Pipeline running task in background?
Afaik AzDo cannot run tasks concurrently. From having had to work with azure pipelines I would highly suggest to use the github approach of Scripts to rule them all and avoiding predefined tasks unless absolutely necessary(Things that are complicated to implement and solutions already existing.
-
Why is uncoupled documentation bad?
GitHub have a pattern for this called "scripts to rule them all" - https://github.com/github/scripts-to-rule-them-all - I've not fully adopted it yet but I probably should, it looks very well thought-out.
-
Script up your projects
People at Github made an attempt to fix this situation: scripts to rule them all. The idea is to have common set of executable scripts for common developer tasks in a script/ directory in the root of every project:
-
How to Join a Team and Learn a Codebase
https://github.com/github/scripts-to-rule-them-all
Buck
-
Go Dependency management in large company projects - How do you do it?
Hyper-large tech companies managing hyper-large monorepos using Bazel (google), buck (Facebook), please (thought machine), pants (Twitter, Foursquare & Square) enjoy them but also have a lot of resources devoted to running and maintaining it.
-
Compiling a single-file app with csc.dll
We use Buck company wide. Our packaging / deployment system, for example, expects to be given a Buck target to build, not a pre-built binary - I can’t just build my app with dotnet and upload it. While it is possible for a Buck target to be a simple bash command (i.e dotnet publish), doing so makes the target “opaque” - Buck wouldn’t have any knowledge of my app’s build graph so I’d lose many of the benefits it gives us (incremental cached builds etc.)
-
Just: A Command Runner
Oh excellent, then better (and more portable!) tools are available:
http://pants.build
https://ninja-build.org
https://buck.build
and, if you hate yourself: https://bazel.build
-
Meta lays off 11,000 people
I’m feeling sorry for everyone affected.
Let’s hope that this isn’t going to impact Buck [0] too much. It’s one of the best things Facebook has ever made.
[0]: https://github.com/facebook/buck/tree/dev
-
Dev Discussions: Everything You Need to Know about Monorepos with Juri Strumpflohner of Nrwl
Pioneered by tech giants like Google and Meta with tools like Bazel and Buck, monorepos are seeing widespread adoption across companies of all sizes and industries.
-
Using URLs for dependency management
Buck has a http_file() that you can use this way, and it has first-class support for Java.
-
Is it possible to be an android developer ONLY with the documentation?
That's a good bridge into saying that we don't use pretty much any standard tooling. Our build system is Buck, we use Mercurial instead of Git, and the IDE of choice seems to be Visual Studio (although Android Studio is supported, with some custom plugins required).
-
Best/Worst C++ IDE you have ever used?
Didn't know it was python based. Their github repo shows 90% of the code is java, only 2% is python. Regardless, C++ build systems should be written by people who are familiar with C++ and the specific problems they need to solve. That means the build system should be written in C++ or C and not in java, lua, or python. I certainly do not want to install python just to build my C++ programs in a CI environment, it just increases my build complexity and attack surface
- Are there any java build tools which have not been written in Java?, If not, what could be the reason?
-
Is anyone using TDD on a significant Android app? Any tips?
The landing page of https://buck.build/ explains some of the most basic stuff. This Meta Engineering blog post summarizes some of the deeper optimizations possible through buck: https://engineering.fb.com/2017/11/09/android/rethinking-android-app-compilation-with-buck/
What are some alternatives?
govuk_design_system_formbuild
Bazel - a fast, scalable, multi-language and extensible build system
django-sql-dashboard - Django app for building dashboards using raw SQL queries
Gradle - Adaptable, fast automation for all
govuk-form-builder - A form builder for Ruby on Rails that’s compatible with the GOV.UK Design System.
Apache Maven - Apache Maven core
generate-package - Use as a sub-generator or plugin in your generator to create a package.json for a project. Or install globally and run with Generate's CLI.
pants - The Pants Build System
pure-sh-bible - 📖 A collection of pure POSIX sh alternatives to external processes.
git-lfs - Git extension for versioning large files
confgen - Generate repetitive configs for vite, typescript, eslint, etc
nvim-lspconfig - Quickstart configs for Nvim LSP