Just a reminder that Tugboat’s our legacy Makefile support ended on October 31, 2018. If you have not already migrated your Tugboat Repositories to the new YAML config file, please see our current YAML documentation to help get you started.
Two weeks ago we released a tutorial on how to integrate the Lighthouse project into your Tugboat Previews, and we introduced a new pricing tier. Be sure to catch those announcements if you missed it.
Today, we are updating our pricing plans and making Tugboat even more accessible to teams.
In this tutorial, we’re going to run a Lighthouse audit every time Tugboat builds out a Preview of our website. If the build is coming from a Pull Request, we’ll also update the deployment status, and post a comment back to the issue with the score results.
Tugboat builds a working preview of your Craft CMS website for any branch, tag, commit, or pull request in a git repository. It can automatically create these previews for pull requests by integrating with GitHub, GitLab, or Bitbucket git repositories.
With the new Docker images in place and the migration to YAML configs, we’re back to incremental release schedules. Here’s what we pushed out this week:
We just launched an update to Tugboat that we have been working on for the last three months. We now support YAML configuration files that live directly in your git repository. Don’t worry; your Makefile build scripts will continue to work until later this year. Here are the new features:
Here’s the latest round of improvements we’ve made to Tugboat:
As many of you know, Tugboat is a wholly-owned subsidiary of Lullabot. And Tugboat was built to empower stakeholders on client projects to see development work as it was ready for review without having the overhead of needing to get a local environment up and running, and up to date.
We are delighted to be one of five companies featured on Gartner’s Cool Vendor list for DevOps list! Tugboat helps customers build higher quality websites, faster, using cutting-edge DevOps. Specifically, we simplify the testing of web applications by automatically generating a clone of the production environment when new code merged in and ready for review. Tugboat stands up a new QA environment when new features are ready for review.
A few weeks ago we announced our plans to switch from OAuth tokens to Deploy Keys or Access Keys for greater security. Our goal is to prevent OAuth tokens from ever touching a Tugboat service. We are deploying this change on Friday, May 18, 2018.