Flags deep dive: Custom technology flags (Semantic code drifts)

The platform provides a the ability to create custom flags based on a set of conditions that the customer can define (a customer can create many custom flags based on their requirements and activate them for analysis).

When to create custom flags?

Leverage this functionality to validate a specific coding expectation which is not represented in the standard technology flag.

Technology.

Classification:

Code

Tools:

Atlassian Jira, Github, Gitlab, Bitbucket.

Intent:

The intent of this flag is to allow the customer to validate a specific coding expectation which is not a part of the standard flag delivered by the platform. For e.g. if the customer wants to analyze potential performance issues in the Node.js codebase then do the following:

• Define a custom flag.
• Specify conditions (that you would like the platform to analyze).
• Perform simulations to ensure that the results are accurate.
• Activate the flag for analysis.

The conditions specified in the flag is used by the Cubyts prediction engine to perform a semantic check of the code based on the following contexts:

1. The code introduced in the current Feature branch/Pull request/Merge request.
2. The data associated with the Feature branch/Pull request/Merge request.
3. The details associated with the linked Jira issue.
4. The outcome of analysis performed by the prediction engine (on the same set of conditions) in other PRs that the engineer has contributed (for a pattern).

The outcome of the aforementioned checks could result in an array of issues in the changes. The platform also provides the resolution path for every issue (which the engineer can copy and apply in the code base).

Configurations:(A custom flag with sample conditions)

(The workflow which allows the user to create a simulation of the results for the specified conditions)

(Sample results)

The flag configurations are the same as other technology flags.