While we continue to publish new features and updates for buddybuild every day, we thought you might be interested in some highlights from the last few weeks…
Our new Selective Builds setting allows you to define which files (or paths) should (or should not) trigger a build of your application when changes are made.
This setting is particularly helpful for teams who:
Build white-labeled apps or use hybrid frameworks like React-Native. If you have multiple apps in a single git repository, you can use Selective Builds to build only the application that was affected by the code change.
Want to skip builds for committed files that are unrelated to your project’s source files. As an example, you may not need to trigger a new build when the
Read more about our new Selective Builds feature on the blog, or follow our step-by-step guide to start using it in your workflow.
How to Use Danger with buddybuild
At buddybuild, our focus is to help automate the tedious and time-consuming aspects of your development workflow to give you the time needed to create great applications. Danger, a popular open source tool, has a similar philosophy - it allows you to automatically apply a common set of rules to code reviews.
To help you streamline the pull request code review portion of your development workflow, we wrote a helpful guide on how to pair Danger with buddybuild - read it here!
A new experience for our Technical Documentation
We recently launched a completely revamped version of buddybuild's technical documentation!
Our new docs experience makes it much easier for you to find, read and navigate any topics you might be looking for help on. Feel free to check out our new version of the technical documentation here: https://docs.buddybuild.com/
In addition to this overhaul, the buddybuild docs are now hosted in a public GitHub repository. Here, readers can file issues for doc improvements, or use the standard GitHub pull request workflow to provide content updates.
By open sourcing our documentation, we hope users can share how they've used buddybuild's features to set up their CI/CD workflows so that others can learn from their experience.
As always, we’d love to hear any questions or feedback you have about our latest features. Feel free to share your thoughts by mentioning @buddybuild on Twitter, or sending them to firstname.lastname@example.org.
If there’s a feature you’d like to see added to buddybuild, please request it on the buddybuild discussion forum. We’re always looking for ways to improve your buddybuild experience!