Introduction
Architecture
Introduction
IntroductionPromote an image in Amazon ECRDownload a file from JFrog ArtifactoryMove or copy an image from JFrog ArtifactoryUpload a file to JFrog ArtifactoryStore an object on Amazon S3Retrieve an object from Amazon S3
IntroductionCreate or update a functionInvoke a function
IntroductionRun an AWS CodePipelineRun a Bamboo projectRun a Bitbucket pipelineRun a CloudBees CI jobRun a CircleCI workflowRun a GitHub Actions workflowRun a GitLab pipelineRun a Harness pipelineRun a Jenkins® jobRun a JFrog pipelineRun a TeamCity project
Check out a Git repository
IntroductionAWS credentialsECR credentialsEKS credentialsGit global credentialsOCI credentials
IntroductionRun Argo WorkflowsDeploy a binary with EC2Deploy to ECSRender an ECS task definitionBuild a container image with KanikoDeploy with OctopusDeploy with Spinnaker
IntroductionHelm chart installHelm chart packageHelm chart publishHelm chart uninstall
IntroductionCreate a Kubernetes namespaceCreate/update a Kubernetes resourceDeploy to a Kubernetes cluster
IntroductionVerify with NewRelic
Execute remote commands via SSH
IntroductionAnchoreAquasecJFrog XraySnyk ContainerSonatype (Nexus) ContainerTrivy
IntroductionStackhawkZAP
IntroductionCheckmarxFind Security BugsGitHub Security ScannerGosecMendNexus IQSnykSonarQube bundledSonarQube
IntroductionMendSnyk
Components

Install the SDK

2 minute read

To use feature management in the platform, install a software development kit (SDK) in the code language of your application.

Client-side SDKs execute code on the client’s device, such as web, mobile, desktop, or over-the-top (OTT) applications. Server-side SDKs are sent to a central server to be processed, and updated using a periodic refresh. Hundreds or more requests can be processed at once, but requests can take longer to process than client-side SDKs.

Because client-side and server-side SDKs work with flag configuration data in different ways, some capabilities and features are only available for a specific type of SDK.

SDK installation instructions

The platform application contains stepwise instructions for installing an SDK. Detailed information on installing each SDK is also available:

Client-side SDK installation:
Server-side SDK installation:

SDK reference

The SDK reference includes useful functions and code examples.

Customer privacy is assured

The CloudBees platform architecture is built around privacy. The platform does not have access to and cannot save end-user data, such as personally identifiable information (PII).

Flag configurations that target specific customers occur on the client side (mobile app, web app, or a backend system) with locally available attributes and are never transmitted back to CloudBees.

SOC 2® is a Service Organization Control (SOC) framework administered by the American Institute of CPAs (AICPA) that assesses an organization’s adherence to the five Trust Service Criteria (TSC). The CloudBees platform is SOC 2 type II compliant.

Resiliency

The platform is protected from outages by using a stateless architecture by default. Each SDK pulls a static JSON file from cloud storage.

The stateless architecture has several key advantages:

  • Scale: It does not matter if you have hundreds of users or millions of users, the SDK fetches a static file.

  • Speed: No computation is done on the CloudBees servers. All flag computation is done in memory on the target platform.

  • Resiliency: CloudBees servers are NOT in the critical path of your software. If the platform is compromised, flags cannot be updated in the UI, but your application is not affected. The SDKs have a caching mechanism. In the case of a network issue, the effects are minimal.

  • Privacy: CloudBees has no access to user private data, which is only stored on the target application.

  • Global usage: CloudBees leverages the power of Amazon CloudFront for its content delivery network (CDN), which provides a unique advantage over competitor products, that report outages in certain geographic areas. Developers need not create proxies or bootstraps that would otherwise be necessary to maintain a connection in problematic regions.

The platform uses Server Sent Events (SSE) to push a message to the SDKs to download a new JSON config file in response to any changes in configuration, so changes are propagated to the clients instantly.
Go