New Environment UX and Admin Role

By Christophe Dujarric, on Aug 17, 2016

Throughout the year, we’ve been working on the “Environment” semantic, which helps you configure Blackfire and its automation features, according to your development and deployment methodologies and tooling.

Lately, we released the new “Builds” UX, which was an essential step towards facilitating the configuration of automated performance tests. The basic principles rely on the fact that an event should be able to start a pre-configured set of performance test scenarios, store the results in a Build, and notify you of the results wherever appropriate (instant messaging, commit status,…).

The last increment includes two major evolutions:

  • All Environment settings can now be changed directly via the Dashboard, in a dedicated settings¬†tab. Previously, this was done via a separate page, which was breaking the user journey and making configuration changes cumbersome.
  • Premium and Enterprise users can now promote collaborators to the Environment Admin role. The Admin can change any environment setting, invite and revoke collaborators (except the Environment owner).

env-ux

This new UX should also help to better understand and use the Environment concept, and how to configure the different sets of server credentials according to your use cases. A simple use case for instance, is to use “My Environment”‘s server credentials on your local machine, while you will configure a server with a shared Environment’s credentials so that you can collaborate with your team, let them profile and run performance tests.

Don’t hesitate to contact us if you have any feedback or struggle with the configuration!

Happy performance testing,

Christophe Dujarric

Christophe is the Chief Product Officer at Blackfire. He's an engineer, but probably one of the least "tech" people in the company. He's wearing many hats, from product management to marketing and sales. He loves the beauty of simple solutions that solve actual problems.