Roost’s environments-as-a-service (EaaS)
Instant & Ephemeral Pre-Production Environments @ Pull Request or On-demand
With the number of services proliferating, developers are working on a smaller and smaller subset of them. The isolation and access to a subset have made effective testing of a service change and Pull Request with dependencies a monumental task. The entire application must be available for accurate testing and certification, which is a time-consuming and daunting endeavor.
Current processes require developers to wait in a queue before their pull request (PR) can be tested or accessible to a QA/staging environment for collaboration and certification. This process delays PRs from merging into the main branch, thus delaying releases. And, to make matters worse, if the PR fails in testing, the whole cycle starts again — consuming resources and time while increasing change failure rates.
It is time for a new software development platform. A platform that provides an on-demand pre-production environment as a service; also available to the engineering team when a PR Create or Merge Request is there (including minimum dependencies needed to conduct thorough testing).
Service dependencies are auto-discovered with Roost.ai environments as a service (EaaS) platform. Pull requests do not need to be put in a queue for testing or wait for availability on a static and shared staging system. Roost environments can be accessed simultaneously by QA teams, software architects, security architects, and team leaders to test cloud-friendly, cloud-native, or container-native applications much earlier in the DevOps life cycle. This strategy significantly eliminates PR deployment delays and therefore reduces cost.
This Roost environment is ephemeral; it gracefully shuts down once testing and collaboration are complete. The environment snapshot is available for future reference or if a replay is needed. The link to the snapshot can be attached to your existing ticketing system. One can add this to the PR merge comments.
This ephemeral environment can be created in multiple ways:
- As part of the Pull-Request life-cycle.
- On-Demand
- Scheduled
- API based Integration
Roost updates service dependencies in a real-time way so that developers always get the latest working environment.
Learn more about the Roost Platform at https://roost.ai
