Introducing: API-parameterized executions

When we develop new features, we try to keep things simple, yet with no compromise to flexibility. A couple weeks ago we delivered parameterized builds. Although it was met with very positive feedback from the community, some users missed the option to parameterize executions via the API as well.

This option has just been delivered: from now on, you can run a pipeline via the API and pass the parameters that will be available in all actions.

Buddy v2.1.16 Released (31-07-2018)

Improvements

  • [Android] It is now possible to deploy builds to Google Play with the ‘Internal test’ flag
  • [Kubernetes] The ‘Show-all’ flag in the get pods method is deprecated and no longer used in K8s actions

Bugfixes

  • The Sentry action is now properly tested
  • Fixed escaping of special chars in the Slack notification content
  • Fixed desktop notifications in the ‘Wait for approval’ action

Introducing: Cron jobs in recurrent pipelines

As you probably know, pipelines in Buddy can be run in three ways:

  • Automatically on push
  • Manually on click
  • Recurrently on time interval

The last method can prove very powerful when properly put practice. For example, you can use it to monitor your servers or backup WordPress sites. However, the recurrent mode lacked advanced config settings, such as running the pipeline only on working days. We have addressed that by adding cron jobs to the pipeline settings.

New mobile version

Web development is a desktop thingie. You sit at your desk, sip coffee, and watch Buddy turn your code into beautifully crafted websites while you give an occasional poke to that Vault-Boy bubblehead you got when leaving your first job at the local burger joint.

Buddy v2.1.15 Released (24-07-2018)

New Features

Improvements

  • [GitHub] GitHub will no longer display terminated executions as ‘Passed’.
  • We now ignore incorrect payloads in webhooks that send information about changes in a private repo (JSON format is required—any other format will be ignored and there will be no info about the commiter on the Activity stream)
  • Added XSS protection when defining ENV VARs
  • [FTPS] The Apache Common library was modified so that it is compatible with Microsoft Windows 2012 FTP server
  • [AWS] AWS CLI has been updated to the newest version. From now, the CLI will be updated automatically with every release
  • [AWS] Distribution ID in the CloudFront action now displays comments for easier identification
  • [K8s] Run Pod and Run Job actions now return logs for all triggered pods
  • [GKE] The situation with basic authorization disabled in the GKE cluster is now handled
  • [Sandboxes] The situation when a Docker image is being used with a user other than root, is now handled
  • [API] Until now, the method that returns commit data was returning only file names. From now on, it returns the list of changed files with full path
  • [API] Authorization of applications that use our API is now secured with 2FA

Bugfixes

  • Browsing workspace activity when another user was deleting the project was sometimes producing ‘Something Went Wrong’ error. Fixed
  • Fixed a display issue when a branch contained # in its name
  • Improved visibility and permission validation in commit scripting
  • The situation with another user opening the details of a commit that was deleted from the repo on the project’s Activity stream is now handled
  • Added escaping of forbidden characters in the Discord action
  • Passing variables with multiline values between actions has been improved

Two-factor authentication (2FA)

In response to popular demand from the raising number of Enterprise clients we are introducing two-factor authentication. You may already know this method from popular services like GitHub or Gmail – now you can use it to secure your workspaces on Buddy.

Get started now

14 days of unlimited trial. No credit card required.