Probo Updates: GitLab Integration, New dbOptions & Varnish YAML Config Options


By: Jason Moore

Last Updated: August 29, 2018

Search Results

This article is included for archival and legacy purposes only. Parts or all of it may be out of date.

The Probo team has been busy working on a few updates. Check out what’s new!

Probo Now Supports GitLab Integration

Similar to GitHub and Bitbucket, users can now log in with their GitLab account and use the Probo.CI app. The Probo open source project already featured GitLab integration.

New dbOptions

We added a Probo LAMP plugin configuration option to set up different MySQL config options typically set in the my.cnf configuration file. This allows users to set up their Probo build’s MySQL configuration to match their production environment more closely. A configuration example for dbOptions in the .probo.yaml file can be found on the Probo LAMP plugin page.

Varnish YAML config options

Our team added a Probo LAMP plugin configuration option to allow users to test out Varnish configurations that match their production environment within their Probo build. The default settings will allow for basic varnish caching to be enabled on a build. This will allow developers to test site configurations and excludes prior to pushing changes to production. A custom VCL file can also be configured to match your production environment even closer with the pathToVcl setting. A configuration example for varnish in the .probo.yaml file can be found on the Probo LAMP plugin page.

Get Started with Probo.CI

Want to Try Probo today?
Get Started Fast!.

When you sign up for a Probo.CI registration code, you will get a two week trial of the plan of your choosing. For more information on how to get started, click here .

LEARN MORE ABOUT PROBO.CI'S PRICING