27 November 2020

Feature spotlight: Windows builds

Feature spotlight: Windows builds

Until now Buddy only supported Linux workers. Bulding .NET applications was only possible through Mono, an open-source implementation of Microsoft's .NET framework. However, this solution, although the only one possible on this type of architecture (excluding .NET Core), was far from perfect, as the build environment was still emulated and not native.

And so it happened: last week we added support for Windows workers (Windows Data Center)! We are super excited about it as it opens Buddy for a completely new ecosystem of developers. It also adds new challenges for our team – as always we are looking forward to you helping us fine-tune the feature so that it meets the high standards of Microsoft developers.

24 November 2020

Buddy v2.3.84 Released (24-11-2020)

Buddy v2.3.84 Released (24-11-2020)

New Features

  • New action: Doctl

Improvements

Bugfixes

  • [Windows build] Fixed a bug with execution retry after a failed Windows build causing the action to crash
  • [Windows build] Fixed a bug with sync paths getting removed upon updating the action
  • [Sandboxes 2.0] Added validation to prevent adding sandbox actions if there's no sandbox in the project
  • [Standalone] Fixed a bug with only the first 100 projects getting listed when adding a project from GitHub Enterprise
19 November 2020

New feature: Execute all pipelines in folder

New feature: Execute all pipelines in folder
Another week, another feature to make your life easier. This time we focus on optimizing pipeline management by introducing an option that will let you run all pipelines from one folder at once.
18 November 2020

In Buddy we trust: Announcing SOC 2 certification

In Buddy we trust: Announcing SOC 2 certification
Ever since we launched in 2016, security has been our #1 priority. With our servers under constant surveillence by SecurityMetrics and regular security audits performed in accordance to the AWS Security Audit Guidelines already in place, we are now ready to announce that Buddy has been officially accredited as SOC 2 compliant.
17 November 2020

Buddy v2.3.82 Released (17-11-2020)

Buddy v2.3.82 Released (17-11-2020)

New Features

  • New action: Windows build
  • New option: Execute all pipelines in the current folder

Improvements

  • Current folder information is now displayed when adding/editing the project's folder
  • [On-premises] You can now manually enter the RAM value for builds in megabytes in the settings

Sandboxes

  • Trying to delete a project with a Sandbox in pending status will now display proper warning

Bugfixes

  • Changelog variables are no longer passed in the SSH action since their potential size caused actions to fail
  • [REST API] Fixed a bug with ref_type and ref_name values not changing when updating pipeline settings
  • [On-premises] Fixed a bug with the display of available seats in the license settings
12 November 2020

Introducing: Priority in pipelines

Introducing: Priority in pipelines
Following last week's [new action modes in pipelines], we're further stretching Buddy's flexibility by adding priority levels to pipelines. In short, priority indicates how soon a queued pipeline will be triggered, i.e. changes the sorting type from run date to priority. In other words, if you have 5 pipelines waiting in a queue and the last one's priority is set to high, it will jump up the line as soon as the current execution has finished.
10 November 2020

Buddy v2.3.81 Released (10-11-2020)

Buddy v2.3.81 Released (10-11-2020)

New Features

  • Priority levels in pipelines – set pipelines to high priority to run them faster when queued

Sandboxes

Bugfixes

  • If deleting a project was taking long, retrying deletion was causing an error. Fixed
  • Private SSH keys defined in the Variables tab will no longer be forwarded to the SSH action
  • Added name length validation when creating a new permission set
9 November 2020

Introducing: New action modes (On warning, On wait for approval)

Introducing: New action modes (On warning, On wait for approval)
Speed, ease of use and reliability are the stepping stones towards creating good CI/CD software. Making the tool flexible enough to cover the growing number of use cases, however, is what makes it great. And this is what we focused on with our last week's release.
5 November 2020

Sandboxes v2.0: Multiple port mapping & authorization

Sandboxes v2.0: Multiple port mapping & authorization
In September 2020, we released new and completely revamped Sandboxes, a functionality that lets developers create staging environments directly from the chosen branch, tag, or pull request. The feature is currently in beta, as we want to ensure that it covers all most popular use cases and everything works flawlessly.
4 November 2020

Introducing: Concurrency slot variable

Introducing: Concurrency slot variable

There is no such thing as one correct approach to Continuous Integration and Delivery. It's possible to distinguish some patterns, yes, but each use case is different and depends on many variables: project guidelines, type of Git workflow, experience and skill of developers, etc. etc.

A crucial element to most delivery pipelines is the testing phase, an essential step to delivering high quality, reliable software. More advanced testing, for example, such as integration, browser, or E2E tests, often require deploying the application to a staging environment first. This may cause issues if you are running tests concurrently for different branches or pull requests. As one of our clients put it: