11 July 2019

New feature: Change user in build actions

New feature: Change user in build actions

Docker flows through the veins of Buddy. It is the fuel that makes our builds run so smooth and simple:

  • First, it launches an isolated container.
  • Second, it downloads dependencies and caches them in the pipeline's filesystem mounted to the container.
  • Third, it runs build commands on repository files.
  • Fourth, it exports the artifacts to the filesystem nad kills the container.

By default, Docker containers are run with the user defined in the image. However, some of you were requesting an option to change the user – and this is what we are delivering this week.

9 July 2019

Buddy v2.2.40 Released (07-09-2019)

Buddy v2.2.40 Released (07-09-2019)

New features

Improvements

  • Attempting to execute commands in the Bash shell in an image without Bash installed returned a wrong message. We have added a hint suggesting to switch to SH instead
  • The capacity of the 'Container CMD' field in the custom services has been extented to 1000 characters

Bug fixes:

  • Repository synchronization errors are now properly displayed
  • In some rare cases, users were charged VAT despite a valid VAT-ID provided - fixed
  • Fixed an issue where Buddy Enterprise users could not add the 'Ghost Inspector' action to their pipelines
2 July 2019

Buddy v2.2.38 Released (02-07-2019)

Buddy v2.2.38 Released (02-07-2019)

Improvements

  • If user did not provide any company details, the invoice will display the owner's name
  • Improved hostname validation of microservices in build actions
  • Improved handling of cache invalidation actions
  • From now on, the Gradle action will use the official Docker Hub Gradle image

Bug fixes

  • It was impossible to delete an integrated project if the user had no administrative rights at the repository provider – fixed
  • Fixed timeout support for the 'Web' and 'HTTP Request' actions
  • Fixed an issue where testing an action configured via YAML did not work properly
  • Firefox input support (e.g password) has been improved
18 June 2019

Buddy v2.2.36 Released (18-06-2019)

Buddy v2.2.36 Released (18-06-2019)

Improvements:

  • Improved support for clone/fetch of custom repositories
  • Reduced waiting time in the Elastic Beanstalk monitoring action
  • Symlinks are now listed in the remote path browser
  • Added support for environment variables in the 'Question' field of the 'Wait For Apply' action
11 June 2019

Buddy v2.2.35 Released (11-06-2019)

Buddy v2.2.35 Released (11-06-2019)

Improvements:

  • Empty lines in the build commands and the environment customization tabs of build actions are now retained
  • New default ENV VARs added:
$BUDDY_EXECUTION_PREVIOUS_REVISION_SUBJECT
$BUDDY_EXECUTION_REVISION_COMMITTER_NAME
$BUDDY=true
  • Improved error support in the 'Find and Replace' action
  • Updated the default commands of the 'Gradle' action

Bug fixes:

  • New pipelines, cloned from a pipeline in a folder, were not automatically assigned to the folder of origin. Fixed
  • Fixed an issue where the 'Lambda Deploy' action did not work properly if the source path was set to a nested path
  • When cloning a pipeline, the trigger condition was not carried over to the new one. Fixed
6 June 2019

Automate infrastructure provisioning with AWS CloudFormation and Buddy

Automate infrastructure provisioning with AWS CloudFormation and Buddy

AWS CloudFormation allows developers to manage infrastructure resources in Amazon Cloud Services across all regions and accounts with a single text file. The new CloudFormation action in Buddy lets you easily deploy, update and remove CF stacks. For example, you can create a pipeline that will perform the following for every pull request:

  1. Provision infrastructure in your AWS account with a CF template file
  2. Deploy your application to the server
  3. Start the application
  4. Run integration tests
  5. Clean up the CF stack once everything is over

Pipeline example

4 June 2019

Buddy v2.2.34 Released (04-06-2019)

Buddy v2.2.34 Released (04-06-2019)

New features:

  • New action: AWS CloudFormation

Improvements:

  • We have increased the max characters limit in the 'Container CMD' field of the 'Run Docker Image' action to 1000

Bug fixes:

  • In some rare cases, after clearing the filesystem the amount of resources used by the account did not change. Fixed
  • Fixed a bug with cluster data not loading upon changing the authorization method in K8s actions
  • The date in default ENV VARs is now properly returned in the UTC format
28 May 2019

Buddy v2.2.32 Released (28-05-2019)

Buddy v2.2.32 Released (28-05-2019)

Improvements:

  • Until now, managing project variables was restricted to admins only. In response to numerous requests, we have decided to extend the privilege to all users with the 'Manage pipeline' permissions set
  • In the Sentry action, you can now add a repository slug. If your Sentry is integrated with GitHub, Sentry will now map the commits from GitHub
  • New default environment variables for Source Control Management system:
    • BUDDY_SCM_PROVIDER
    • BUDDY_SCM_URL
  • You can now see the YAML-configured pipeline settings in the GUI. From there, you can also make changes and generate a new YAML for the selected pipeline

Bug fixes:

  • Fixed an issue where providing a path to a data file caused the Ghost Inspector action to fail
22 May 2019

Monitor build status with Datadog Service Check

Monitor build status with Datadog Service Check

Buddy offers a dedicated set of actions allowing you to send deployment details to your favorite monitoring service. One of the most popular tools is Datadog, now complemented with an individual action which updates the service with the status of the build after the execution.

App monitoring actions

21 May 2019

Buddy v2.2.31 Released (21-05-2019)

Buddy v2.2.31 Released (21-05-2019)

Improvements:

  • Improved support of variables during the action testing
  • VAT information is now displayed in the billing tab

Bug fixes:

  • Fixed an issue where pushing changes to YAML configuration while the pipeline was still in progress stopped the pipeline from being run on push
  • The link to the execution triggered by the 'Run next pipeline' action is now properly displayed in the action's execution details
  • If creating a folder during the deployment failed, the second attempt was always failing. Fixed
  • Slack attachments will now properly support variables with new lines
  • You will no longer see two confirmation notifications when deleting a project
  • Fixed a bug that did not allow to select the free plan during the trial period