We’re thrilled to announce that repository-level user permissions have shipped! Now different users can have different levels of access on a per-repo basis. That means no more needing to have multiple Tugboat projects to manage user access. With repo-level perms, organizations can handle all the repositories of their org from a single Tugboat project, all on a single Tugboat plan. And to top it off, you can still mix and match repos from any Git provider.
It’s been about a week since Tugboat’s principal engineer Ben Chavet, passed away from Covid pneumonia. Wrapping our heads around the loss of our soft-spoken, brilliant, and eager-to-help friend and colleague is next to impossible. So, we reflect.
We are excited to partner with Contegix to offer Tugboat on their FedRAMP-authorized PaaS.
You may have noticed a row on our Pricing page entitled CPU. Like this:
If you think you can’t afford to implement a high-quality software development process, think again.
We’re not just a Support channel anymore! Today, we’re excited to officially (re)launch Tugboat’s Slack Community!
The primary reason we don’t take the time to set up automated review environments in our development workflow is that the process of getting to automation is front-loaded and hard. It requires you to sit down and codify every decision and failsafe necessary to deploy your infrastructure. However, the benefit of doing this work is developers can now use infrastructure like they use code, and they can spin up what they need when they need it.