June 13, 2017
- 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
Customer Success Manager
A story-teller and conversation-lover, Alexander decided to invest his skills to help his friends at Buddy transform the cold language of patch notes into exciting narratives. Also: an avid gamer, hip-hop DJ, Liverpool FC fan, absentminded husband, and the father of two.