This lexicon is a collection of terms and definitions used by CloudBees.
The ability to request review and approval for flag changes before they are implemented. This capability allows companies that require a higher level of governance to enforce change management policies and to stay compliant with SOC and SOX requirements.
Allows users to create, update, or delete feature flag configurations as a part of build steps within the continuous integration workflows.
The plugin communicates via the REST API to enable the required task for a feature flag configuration to be automated within Jenkins.
A fully-featured, cloud-native capability that can be hosted on-premises or in the public cloud to deliver CI at scale. It provides a shared, centrally managed, self-service experience for all your development teams running Jenkins. CloudBees CI on modern cloud platforms is designed to run on Kubernetes. CloudBees CI on traditional platforms has been developed for on-premises installations.
An advanced feature flagging solution that lets your development teams quickly build and deploy applications without compromising on safety. By providing a gradual release mechanism and a simple way to define target audiences, CloudBees Feature Management allows developers and product managers to optimize feature releases and customize the user experience. CloudBees Feature Management gives teams control over features that are in staging, production, or any environment in the deployment pipeline.
A software development process used to remotely enable or disable functionality without changing code. Flags can be toggled on or off while in production. They assist in helping teams achieve continuous delivery with less risk, and can be implemented on the client or server side.
The value of the flag that is created when defining flags in the code. Default values are mandatory and flags cannot be created without them. They will be served when there is no configuration available (for any reason) or no other value overrides it.
A view used for testing purposes by allowing developers to expose a view that shows the current status for each flag and allows users of flags to override the flag. This view is usually only exposed to developers, the QA team, and the product team.
A way to allow application code, using one of the CloudBees Feature Management SDKs, to proxy all network traffic to the CloudBees Feature Management backend services. This is useful when applications using CloudBees Feature Management need to be run in a private or secured network without access to the internet.
An open standard for exchanging authentication and authorization data between parties, in particular, between an identity provider and a service provider.
Users are able to sign in to multiple software applications using the same sign-in details with SAML.
Enables enterprises to optimize their software delivery process for increased innovation and security by connecting, automating, and orchestrating the tools and functions across development, operations, and shared services teams.
Allows you to create flags and custom properties based on how the secret is defined. When enabled on the app, and defined in the Rox SDK setup code, the code can be seen in the installation instructions on the CloudBees Feature Management GUI.
A distributed algorithm that determines the percentage of users the flag will be rolled out to. This algorithm is similar to tossing a coin, but once a coin is tossed the result is consistent for a feature flag.
A body of users that flags can be targeted for or against. Target groups are based on the audience configuration. Target groups can be segmented by user properties or device attributes such as geographical region, browser, email, or custom attributes like Plan Type or Account ID.
A real-time notification in CloudBees Feature Management that is triggered when an event happens in the system. Webhooks can be configured to listen to events within a specific environment or all environments.