🗺️ Run locally

Bit CLI defers component build processes during snap or tag commands, delegating them to Ripple CI during the export stage. This allows you to leverage Ripple CI even when working locally.

bit snap --message 'i made some changes'
bit export
Copied

The terminal output will provide a link to the Ripple CI job:

exported the lane scope/my-lane and the following 2 component(s):
foo/bar
sun/moon

Visit the link below to track the progress of building the components in the cloud
https://bit.cloud/scope/~lane/lane/~ripple-ci/job/job-name
Copied

You can opt to use an existing CI tool for component builds. This requires setting up automation scripts and hooks (listed below).

To snap or tag components and execute their builds locally, use the --build option:

bit snap --build
bit tag --build
Copied

To entirely bypass Ripple CI, configure Bit to force local builds using either the Bit configuration or an environment variable:

bit config set force_local_build true      // Bit configuration
export BIT_CONFIG_FORCE_LOCAL_BUILD= true  // Environment variable
Copied

Utilize the following scripts to integrate your preferred CI tool instead of Ripple CI:

• GitHub Actions
• Azure DevOps
• GitLab CI
• Jenkins
• Other (bash scripts)

• Contact support
• Join Bit Slack community