28 March 2019

New feature: Version History for Pipelines

New feature: Version History for Pipelines

The core principle of Continuous Delivery is to version everything and everywhere: not only the source code, but also things like configuration files or SQL’s used for database migration. In 2017, we introduced YAML configuration for pipelines, enabling you to store pipeline configuration in the repo as buddy.yml. This way developers could easily track the changes to their workflow.

Today we add the option to browse pipeline history in projects configured with the GUI.

26 March 2019

Buddy v2.2.15 Released (26-03-2019)

Buddy v2.2.15 Released (26-03-2019)

New features:

Improvements:

  • [HTTP action] The log now contains the URL address and the payload
  • [Run next pipeline in YAML] From now on you don’t need to know the ID of the pipeline that you want to run. Instead, you can define next_project_name and next_pipeline_name
  • [Copy files in YAML] From now on you don’t need to know the ID of the pipeline from which you want to copy files. Instead, you can define source_project_name and source_pipeline_name instead
  • [Build/Run Docker Container in YAML] If you want to use the previously built image, just enter the name of the action in which it was built: docker_build_action_name

Bug fixes:

  • Authorized apps in my-ID are now loading faster
  • Fixed a bug with the Elastic search microservice in versions lower than 3.0.0 not starting properly
  • The remote_path in the Google CDN action couldn’t be set in the REST API and in YAML. Fixed
  • If the payload of the ‘HTTP’ action or the attachment in the ‘Slack’ action contained a variable with newline characters, the JSON sent was incorrect. Fixed
  • Fixed a bug with parallel actions using different images causing errors in the executions
  • Fixed a bug with recovery codes not working for turning off 2FA. Thanks for pointing that out, Aubrey!
19 March 2019

Buddy v2.2.14 Released (19-03-2019)

Buddy v2.2.14 Released (19-03-2019)

New features:

Improvements:

  • It is now possible to change the workspace owner in the workspace preferences
  • You can now enter the path prefix at the ‘Purge everything’ option in the AWS CloudFront action
  • From now on, you can use ed25519 keys with a passphrase in the SSH/SFTP actions
  • Notification actions have been redesigned for better

Bug fixes:

  • Fixed a bug with GitHub repositories not synchronizing correctly if they contained 1000+ pull requests
  • In some cases, pipelines with the ‘Terminating’ status were blocking the global execution queue in the workspace. Fixed
15 March 2019

Scheduled Server Upgrade [March 18-23]

Scheduled Server Upgrade [March 18-23]

Dear developers, From March 18 to March 23 we will be upgrading the system on our build servers. There will be no downtime whatsoever, but some of the pipelines might be temporarily run without the cache, which will prolong the execution time.

The slowdown may happen only once per pipeline, and concerns only 20% of all our users.

If you wish, you can reach out to us on support@buddy.works or on the live-chat, and send the URL to your account – we’ll check if your workspace is among those 20% and send you the list of pipelines that may be affected.

Thank you for understanding and sorry for possible inconvenience.

You can subscribe to automatic notifications on the status of our servers on our Status Page

14 March 2019

New design of deployment actions

New design of deployment actions

“Clean”, “intuitive”, “easy to use” – Buddy’s UI is probably the most praised feature of the service, which makes us extremely proud. Of course, it’s not about bells & whistles just for the sake of it – every single element has been carefully crafted to help developers introduce CI/CD with as little effort as possible.

However, we’ve been adding new features for so long now that the time has come to clean up the house and move some furniture.

12 March 2019

Buddy v2.2.11 Released (12-03-2019)

Buddy v2.2.11 Released (12-03-2019)

Improvements:

  • New, more intuitive design of all deployment actions (including SSH)
  • Added a new action called ‘Prepare Environment’ that is automatically run before every execution. The action is available in the execution details and shows logs from clearing the cache, fetching the repository and setting the variables
  • New events on the Activity stream: Add / Edit / Delete Environment Variable
  • It is now possible to set timeouts in the ‘Web’ monitoring action

Bug fixes:

  • Sometimes when an execution was terminated during the deployment, not all uploaded files were shown in the log. Fixed
  • Fixed a bug with cache clearing during the execution which caused the filesystem to be empty empty during that execution
  • Fixed a bug with updating credentials in projects from a custom repo
  • Fixed a bug with the / character in variables not working correctly
5 March 2019

Buddy v2.2.10 Released (05-03-2019)

Buddy v2.2.10 Released (05-03-2019)

Improvements:

  • Slack action now supports listing 1000+ channels

Bug fixes:

  • Fixed a bug with the ‘Run next pipeline’ & ‘Copy files’ actions failing when the child pipeline was inactive (e.g. due to failed YAML processing)
  • Better error handling for access/secret keys credentials in AWS integrations
  • Current usage was displayed incorrectly for some accounts — fixed
  • Fixed a bug with the SSH action checking for Base64 when connecting to a server with the Alpine system
  • Fixed a bug which caused that ignoring the errors in SSH action was not working when the ‘Run as script’ flag was checked
  • Fixed a bug with uploading themes for Shopify
  • In some cases, actions which were using previously built Docker images and also were configured in YAML were not working properly — fixed
  • Adding another parallel section in the pipeline was resulting in an incorrect error about insufficient parallel actions — fixed
  • Fixed a bug with the displayed stacktrace when the error was not handled — thanks for the heads up, Ashish!