May 10, 2016
Changelog: May 10, 2016
In the last two weeks we worked hard on improvements to the speed and UX to make it easier for you to fall in love with Buddy. Perhaps the most important feature of this release, however, is adding services to the builds, just like we promised. What feature would you like to see in Buddy in a future release? Drop a word in the comments or hit me on email. Always happy to hear from you guys.
New Features and improvements
The feature lots of you've been asking for is here: you can now use databases of other services during builds. Hooray! \o/
While adding services we also changed the build action view to make the configuration process easier.
Managing pipeline workflows is also fancier and easier to use. We like to give stuff additional polish.
You don't have to define the branch or the wildcard for a pipeline if actions don't require it. For example, you can create a pipeline with a monitor action that once a minute will check if your website is up and running.
Branches and pipelines views will now work faster thanks to optimizing the method responsible for returning
commits ahead. We like to make things work smoother, too.
You can now name your Docker file anyway you want: - it doesn't have to be "dockerfile" anymore. How about "buddyfile"?
Yet another Docker build improvement: now you choose a specific Docker file, not the whole directory. This means you can keep different Docker files in one folder. Docktastic!
You can now use
~/in deployment actions to set the home path.
The list of executions has been, guess what?, optimized. From now on we don't keep executions older than 15 days; the last 200 executions are never removed.
Some of our existing users used to log in to the service with "Sign up by GitHub" and had to go through the tutorial wizard every goddamn time. We understand that - we're lazy, too. From now on you can log in with the sign-up button so you can begin procrastinating faster.
We've added some new execution information in API because of the changes to the default payload in HTTP POST.
On rare occasions, upon terminating an execution some actions were still displayed as in progress. Fixed.
Some of our clients have reported a bug with group permissions in GitLab causing errors in the list of projects. Fixed.
There was a bug with capital letters in the email address which caused problems with logging to the service. Fixed.
For now the Git push action only supports HTTPS. However, the action lacked a validator and that excluded URLs with SSH protocol. We've added it. We're going to add support for SSH soon, too.
If one of pipeline executions has been skipped and the following has failed, the action 'on failed' didn't execute properly. Now it does.
There was a bug with choosing the remote path in one of the most popular import methods. Now there isn't.
Customer Success Manager