Sisense Gradual Rollout Process

The Sisense gradual rollout process is a systematic, controlled method for delivering new versions, which includes major releases and service packs, containing new features, improvements, and bug fixes, to production. It is designed to minimize risk and ensure quality by exposing updates to a limited audience before a full-scale release. Here’s an overview of how the process works:

  1. Internal Testing

    Before any external rollout begins, new versions undergo extensive internal testing to ensure that the functionality meets quality standards and that any potential issues are caught early.

  1. Staged Deployment (the beginning of “Cloud Availability”)

    Once internal validation is complete, the new version is deployed to a small, representative subset of Sisense cloud customers. This phase allows Sisense to monitor the version’s performance in a real-world environment without exposing the entire user base to potential issues. During this phase, key performance metrics, error logs, and user behavior are closely observed.

  1. Monitoring & Feedback Collection

    As the version is rolled out gradually, Sisense collects quantitative data (like performance metrics, error rates, and resource utilization) alongside qualitative feedback from early users. This continuous monitoring is crucial to detecting any anomalies or issues that might not have surfaced during internal testing.

  1. Incremental Expansion

    As issues that are identified are addressed, new builds are created, and the deployment is progressively expanded to larger segments of the user base. Each expansion step is accompanied by further monitoring and validation, ensuring that the version remains stable as usage scales up.

  1. Full Rollout - GA ("General Availability")

    Once the version has proven stable and initial issues have been addressed, it is rolled out to the entire user base - both cloud customers as well as on-prem customers. From the beginning of the Gradual Rollout process until GA usually lasts approximately one month.

Note:

The majority of cloud customers are upgraded just before or upon GA, so they will have the latest build. However, customers who receive an earlier build during the rollout process may not receive the later build upon GA. Therefore, some features, improvements, and fixes listed in that version’s release notes may not exist in their build, but will be included in their next upgrade. There are changes to this process planned for the future, which will be communicated when relevant.

Overall, the Sisense gradual rollout process balances the need for innovation with the imperative of maintaining a reliable, high-performance environment for all users. By progressively exposing changes and rigorously monitoring their impact, Sisense can deliver improvements confidently while minimizing risk.

For more information, see: