SFTP, SCP, Rsync, the good old FTP – there are many ways to deliver an app. The choice depends on many factors, such as working speed, infrastructure limitations (some servers allow only FTP upload), or developer preferences.
Some time ago we made an analysis of what our clients use for application upload. The clear winner was the FTP protocol. Right after it, there were SFTP and Rsync. However, in this post we’d like to talk about the fourth contender that only just missed the podium: Git.
New Relic is a tool that lets you monitor and optimize the performance of your application and production server. It is widely used by thousands of developers across the world, including the Buddy Team.
Don’t skip flag. A single pipeline cannot be undergoing more than one execution at a given time. In other words, if the execution is in progress and another user runs the pipeline, the second execution will be queued and won’t start until the first one is over. However, if there are more executions in the line (for example 5), Buddy will only run the newest execution (5) and skip the rest (2-4). From now on you can check Don’t skip in the pipeline and Buddy will run all executions one by one. This feature is useful if you want to check every single commit for errors
You can now parameterize the URL address in the Web Monitoring action with env variables and Buddy parameters
From now on the errors thrown on the server side by HTTP requests will be covered in a detailed stacktrace in the action logs
You can now temporarily disable specific actions in the YAML file by adding "disable: true" to the action properties
When two or more pipelines were triggered and queued, the pipeline that was triggered last was executed as the first in line. From now on the pipelines will be executed in the natural order they were run.
One of our clients (cheers Mike!) reported a problem with fetching feeds on the Activity stream. We’ve changed some indexes in Mongo DB and fixed it
Fixed bug with running pipelines with HEAD revision set fetching the revision from the default branch instead of the branch set in the pipeline
After one year of testing, we have decided to shut down the beta of Sandboxes. Using the feedback that we gathered, we are currently working on a new and improved version of the test environment feature. Make sure to follow us on Twitter for news and updates on the release date.
It’s been a busy couple of months for the team at Buddy.
As you can learn from our weekly newsletter, we’re doing our best to drop new features regularly, their priority always reflecting current demand from the community. Here’s a few words on what we’re working on at the moment, and what we’re cooking for the months to come.
With the rising popularity of Webpack more and more people start comparing it with Gulp.
Fierce discussions populate comment sections of web development websites about which one is better. In this article we’ll show you what Webpack is, how it differs from Gulp, and – most importantly – which one you should use.
Environment variables are now supported in private_key and passphrase inputs of the Git Push action
Due to different server configurations of our users we have decided to remove remote directory validation on the server—there will be no more problems with adding SSH actions. NOTE: if the specified directory does not exist on the server, the first execution will end as failed
You can now use the filesystem in pipelines with branch assignment set to ‘None’
We’ve changed the way pipeline statistics are generated so that they’re much more clear
Fixed bug with incorrect date of the last change to a directory or file in the Code tab. The date is generated with git log: sometimes a wrong parameter was applied and the last revision was not fetched, which caused the website to crash
Basic authentication for the HTTP Request action was only served in the POST method. Now the rest of methods is served as well
Everybody knows what it is, almost everybody has already used it. Slack is the most popular notification action in Buddy, with over 24% of all (!) accounts using it. At this rate, the email and mobile notification will soon be passé, with Slackers taking over the world.