bors-ng
shipit-engine
Our great sponsors
bors-ng | shipit-engine | |
---|---|---|
14 | 5 | |
1,516 | 1,392 | |
- | 0.6% | |
7.2 | 7.7 | |
25 days ago | 7 days ago | |
Elixir | Ruby | |
Apache License 2.0 | MIT License |
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.
bors-ng
- Bors: Elixir GitHub bot that prevents merge skew / semantic merge conflicts
-
How do you WORK WITH testing teams?
You can further protect main branch by using a rollup approach (see Bors for an example) where the pre-merge tests are run against the combination of those PRs currently proposed for merging, which limits the possibility that two PRs look OK but together break something.
-
Bors-NG, declared to be feature frozen and deprecated
Completely independent implementations of the same underlying concept, one of which was written pretty much just for the rust project, and the other was written as a more general tool and service.
-
Merge Commit, Squash, or Rebase: how do you close Pull Requests on GitHub?
Merge commit (via bors) because I hate squash merges.
-
What’s a bors, and why (don’t) you want it?
Maybe the author does not know that there's https://bors.tech which is a publicly available Bors instance. There's absolutely no operational cost involved except for the initial setup.
-
Two Years and over 700 Websites Later
Or images. On pages like https://bors.tech and https://foodpartners.us the "bloat" is all images. The images are bigger than they were in the 1990's because they look better, even if you don't think they communicate more "information" people may still want them.
-
Ask HN: How are pull requests integrated in a repo with high commit frequency?
According to the README, it bisects. It doesn't matter much for me, though - the batches in our case were never big.
https://github.com/bors-ng/bors-ng/blob/master/README.md#how...
-
This is how auto-merge works at Bumble, how we optimised processes and removed restrictions on the number of tickets per day
Sounds like they settled on the bors model of a batching merge queue. Gitlab's merge trains instead speculatively run all of the merges at once which gives more precise data at a higher cost and longer time, if your number of parallel runners is limited.
- Launch HN: MergeQueue (YC S21) – Automate rebasing and merging for your codebase
shipit-engine
-
What are you allowed to put into your personal github, from a job?
For example: shipit was a homebrew deployment system Shopify made, and they open-sourced it because there's nothing about how they ship their code that's a trade secret or worth hiding.
-
Faster Ruby: Thoughts from the Outside
> Usually that was in the form of long-running network calls.
That's why doing a network call to another service in the middle of a request is pretty much banned from the monolith. Anything that doesn't have a strict SLO is done from background jobs that can take longer, be retried etc.
Now you mention FedEx so I presume you were working on the shipping service, which by essence is kind of an API bridge so it's probably why it was deemed acceptable there, but that's far cry from what a typical Rails app look like, except maybe in companies that do a lot of micro-services and are forced to do inline requests.
> that's not a use case that Ruby/Rails are built to elegantly handle.
I'd argue the contrary, the elegant way to handle this is to perform these calls from background jobs. Look at shipit [0] for instance, it's syncing with the GitHub API constantly but doesn't do a single API call from inside a request cycle, every single API call is handled asynchronously from background jobs.
[0] https://github.com/Shopify/shipit-engine/
-
Ask HN: What are some open-source continuous deployment tools?
My team is evaluating different deployment tools to replace our homegrown solution.
There are plenty of continuous integration tools (GitHub Actions, CircleCi, etc.), but adding deployment aware logic like canary deployments and having an audit log of deploys requires adding lots of code which I'd rather not maintain.
I'm looking for tools focused on code deployment. A quick search turned up shipit (https://github.com/Shopify/shipit-engine) and teletraan (https://github.com/pinterest/teletraan).
Are there other open-source deployment tools like those projects?
- Launch HN: MergeQueue (YC S21) – Automate rebasing and merging for your codebase
- Ask HN: How do you keep track of releases/deployments of dozens micro-services?
What are some alternatives?
rust-cache - A GitHub Action that implements smart caching for rust/cargo projects
backstage - Backstage is an open platform for building developer portals
cargo-xtask
crane - ⬆ A GitLab CI ready image to upgrade services in Rancher
marge-bot - A merge-bot for GitLab
teletraan - Teletraan is Pinterest's deploy system.
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
aws_lambda_runtime - An AWS Lambda runtime for crystal.
htmlbutcher - HTMLButcher is an advanced HTML slicing tool
reliza-cli - CLI to interact with Reliza Hub
ZudVPN - A mobile application to deploy private VPN servers in the cloud with DNS ad-blocking and other features
riff-raff - The Guardian's deployment platform