Roost — a new and unique way to do CI, your changes are always production-ready

What is the primary purpose of CI? Keep integrating your code/change continuously and in an automated way?

Companies are breaking down applications into function-based services. And we are making the services tiny; the need for integration & end-to-end testing is mainly at the HTTP interaction level only.

What if a service change is tested automatically and continuously with dependent services & production configuration? Do we still need CI, or can we just integrate with a CD tool?

Roost eliminates the need for CI in a unique and left-shifted way. Any change, Roost creates and tests those in disposable and sharable pre-production environments. One can define production configuration in Roost SaaS Control Plane; Roost will use those configurations to run tests. In that way, Roost handles tests and checks of your changes and then notifies you of any issues or successes.

Once Roost runs those tests for you in a production-like environment, it marks those changes as certified. Once the change is committed and certified, Roost will integrate your change with your existing CD pipeline.

This way, your changes are always production-ready, and the traditional CI phase is not needed anymore. Furthermore, once these changes go to production, the chances of failure are close to none.

Therefore, Roost shortens your development & deployment pipeline and speeds up your changes/releases to production.