CI/CD Integration

User Problem

Users currently lack a streamlined, automatic way to integrate their application publishing workflow from Plotly Studio/Cloud directly into their existing Continuous Integration (CI) process. This requires manual steps to move code to a repository, trigger builds, and then publish the final, tested application back to the hosting environment (Plotly Cloud or Dash Enterprise), leading to increased effort and potential for error in maintaining code quality, versioning, and documentation.

What is it?

The feature is an Automated CI/CD Pipeline Integration that connects the application publishing process within Plotly Studio (and Plotly Cloud) directly to a user's registered code repository and CI system (e.g., GitHub, GitLab, Jenkins). It uses a dedicated, system-connected application (like a new GitHub App) to manage the secure transfer of code and the final deployment.

What does it allow users to do?

This integration allows users to:

• Automatically Commit and Push Code: When users choose to "publish" their application, the system first automatically sends the application's code to their designated code repository.

• Trigger a CI/CD Pipeline: This code push automatically initiates the user's defined build and testing pipeline within their CI system.

• Customize Workflow Actions: Users can configure their CI pipeline to perform necessary pre-deployment actions, such as:

  • Automated Versioning: Setting and stamping unique version numbers on the application.

  • Documentation Generation: Creating up-to-date documentation based on the codebase.

  • Code Quality Checks and Testing: Running comprehensive unit, integration, and security tests.

• Seamless Deployment: Once the CI pipeline successfully completes all checks and builds, the connected application (e.g., the new GitHub App) receives a signal and securely publishes the final, validated application to the target hosting environment, such as Plotly Cloud or Dash Enterprise. This removes the need for manual deployment steps post-CI.