This lexicon is a collection of terms and definitions used by CloudBees.
Specific access permissions grants to users and teams. In the CloudBees platform, access control is role-based.
A custom platform application that performs complex but frequently repeated tasks. An action serves as the starting point for a commonly used task, such as checking out a repository.
Refers to any the following:
The assessment of software development process, performance, security, and testing. The CloudBees platform has the following analytics dashboards:
A manual workflow step before executing a new step, which pauses the run until a pre-configured user, known as the approver, responds to the request and approves it, allowing the workflow run to continue.
Securely verify the identity of a user. The following types of authentication are available for the CloudBees platform:
A dashboard to provide Jenkins and CloudBees CI operations data in a consolidated view. These metrics help administrators monitor pipeline health, proactively address high-volume peaks, and enable their teams to run more efficiently.
A continuous integration (CI) tool, such as CloudBees CI or Jenkins®.
A metric that measures code additions and deletions during software development.
The change in commit activity over time, including commits per active developer.
A piece of software, built and, if desired, released and deployed from source code. A component is contained in an organization or sub-organization.
Refers to any the following:
A packaging of everything your software needs to run, including code, libraries, and any other dependencies. Registries are a secure way to store and share container images, and with the CloudBees platform, you can build and publish container images.
Continuous delivery is a DevOps software development practice that prepares software for release to testing and/or production environments. The goal of CD is that the software is always in a releasable state. Continuous integration (CI) can be combined with CD to implement an automated software delivery process.
The logical extreme of software development is to automate deployment to production for every change that passes automated tests, a DevOps practice called continuous deployment. Continuous deployment is often confused with continuous delivery (CD), but they are separate practices. Continuous deployment works for web services, but not for software such as mobile apps or in highly regulated environments that require manual deployment. CD works for all kinds of software.
A DevOps practice in which every time a developer commits a change, the entire application is built and automated tests are run against it. If the build or test process fails, the development team can fix the problem immediately. The goal of CI is that the software is always in a working state. CI tools invoke the jobs and automatically build and run unit tests on the latest code changes, helping you quickly find and address bugs, improve software quality, reduce time to validate, and enhance software updates.
Create properties for feature flags for use in targeting users. Configure custom properties in either the application code or in the UI.
The use of feature flags to progressively toggle features on and off for certain segments of users.
A conditional statement around a coded functionality to manage features in an application. If a feature flag is toggled on, code within the conditional statement is skipped and the feature is disabled. Otherwise, the conditionals are commented out, and the code within the conditionals runs as usual.
Flow metrics is a framework that connects business strategy with software delivery, by providing a view of value flow and correlating it with expected business outcomes. Five flow metrics are calculated in the platform:
A count of a feature flag evaluation. Impressions data defines the flag activity status.
A standard interface connecting two or more systems. Use integrations to facilitate communication and data exchange between different applications, resources, or services.
An open source automation server. With Jenkins, organizations can accelerate the software development process by automating it. Jenkins manages and controls software delivery processes throughout the entire lifecycle, including build, document, test, package, stage, deployment, static code analysis, and much more. You can set up Jenkins to watch for any code changes in places like SVN and GitHub, automatically run a build with tools like Ant and Maven, utilize container technology such as Docker and Kubernetes, initiate tests and then take actions like rolling back or rolling forward in production.
Workflow steps are grouped into jobs within a workflow. A job is defined by the jobs keyword in the workflow YAML file.
A transformative approach to software testing through AI-powered insights that optimize testing workflows. By leveraging machine learning, Launchable intelligently selects and prioritizes the most important tests with the highest potential impact, significantly reducing test cycles and improving the accuracy of test results.
An auto-generated file for the workflow run that contains information about activities for diagnosis in case of failure. All run errors are highlighted in log files to assist in fixing issues.
A message configured to be sent to specific users about events in an organization. The following notification types are available:
Measurement of the internal states of a system by examining its outputs. CloudBees platform supports the NewRelic observability tool.
Key/values exposed by an invoked CloudBees CI or Jenkins® pipeline. These outputs can be passed from a CloudBees CI or Jenkins pipeline to the platform.
The ability to update a property to a specific value. You can edit any property in the CloudBees platform that does not have Prevent override selected.
A grant of specific access to entities within the CloudBees platform. The only way to provide permissions is through assigning a custom or predefined role to an account holder. Each predefined role has a set of permissions already configured. Every role contains one or more permissions with privileges set.
A method for adding functionality to a CI tool. One or more plugin installations are required to integrate a CI tool with the CloudBees platform.
A platform action set up with defined values, such as access tokens, URLs, and settings to simplify workflow configuration. A preconfigured action is ready for use without the need to repeatedly input sensitive or commonly used general information.
A key-value pair of data used to configure entities, such as an action, an environment, or an integration.
Enables users to cache Docker images locally, reducing reliance on external registries such as Docker Hub. By configuring a registry mirror, you ensure more reliable and faster builds while mitigating issues related to external service outages.
A set of access permissions for an account holder, who can have multiple roles in an organization. Roles may be either predefined or custom. A role can be granted to define fine-grained permissions at either the organization or component level.
Secure control over access by granting permissions through roles defined for specific users and teams. Roles may be either custom or predefined, and multiple roles are allowed. Set specific permissions at either the organization or component level. Each permission has five different levels of privilege, to enable fine-grained control of access.
The execution of a workflow, either by an event, or manually.
A standard for exchanging authentication and authorization data between an identity provider and a service provider. SAML is a common single sign-on (SSO) configuration that allows users to sign in to multiple software applications using the same credentials.
An automated process to execute an activity on a specific date.
To use feature management, an SDK must be installed in your application. Feature management SDKs are available in numerous code languages A unique SDK key is generated by the platform to connect and serve feature flag configurations to a codebase.
Specific access permissions grants to users and teams. In the CloudBees platform, access control is role-based.
A property that is encrypted to protect sensitive information, such as a password or an API key.
An authentication tool that enables you to securely sign in to multiple software applications using one set of credentials, providing a more streamlined user experience. The CloudBees platform single sign-on (SSO) supports security assertion markup language (SAML).
Software delivered over the internet rather than being on-premise. The CloudBees platform is cloud-native, so each customer can have their own version of the application, configured to their specifications, but from a shared code base that is updated and maintained by CloudBees.
Can refer to the current condition of:
A workflow task within a job that executes commands or actions. Because step commands run in their own containers, any changes to environment variables or other local filesystem directories are not saved as the workflow runs from step to step.
The stickiness behavior of a specific feature flag determines what value a user should receive when served values are split. The default stickiness property is distinct_id, but any property can be used. You can override the default stickiness property to create a consistent cross-platform audience experience for split releases.
A type of team provided by the platform, and not created by an administrator. System-generated teams simplify adding new account holders to an organization by automatically providing a set of permissions based on team membership.
Create a target group in feature management to specify the audience for feature flags. Each member of a target group shares a specific property or attribute, such as an email domain, a geolocation, or a software version. Simplify flag configuration by using the same target group, such as for internal testers, for multiple flags.
A group of account holders within an organization that can be assigned common permissions. Define a custom team for a specific component or access level to provide only the minimum level of access needed for a group to perform their job function. Use System-generated teams, either User (System) or Admin (System), to set appropriate access for users at the time they are invited to the organization.
Provides a view in the UI of system performance, error handling, robustness, and scalability of your software when it is run beyond normal capacity. The platform can collect test results from workflows and CI pipelines and publish the data to the Test insights dashboard. Filter the data by component and time frame.
Use unit tests, UI tests, and integration tests in your workflows to maintain code quality and accelerate deployment. The platform can collect test results from a workflow and publish the data to the Test insights analytics dashboard.
The execution of a workflow, either on demand or in response to an event. A push to a specified repository branch or a pull request are event-driven triggers. Use a manual trigger to run a workflow on demand. You can also use a platform-generated API to trigger a manual workflow.
A lean business practice that helps measure the business value of every software development activity. VSM dashboards include:
A configurable process, defined in a YAML file, that runs jobs. Use workflows to automate software development and delivery. Create and manage a workflow using the workflow composer.
The dashboard for creating and updating a workflow, that includes both a visual tool and a code editor. The visual tool and the code editor sync automatically, so a change in one results in the same change in the other, and you can use both to create or update a workflow.