Page Comparison

Using Roost, you can configure once and enjoy automated preview environments. These environments provide you a number of benefits:

Ready Ephemeral environment created real-time with your current code changes and ready to be used by all.
Immediately accessible as well as shareable across different stake-holders
Certification of your changes against the existing test-suite. Prevents any loss of time over not-so-ready changes
Identifies changes that are breaking and prevents any production issues OR time lost towards manual QA/testing.
Controlled cloud cost as environment auto expires after a certain time.
Central dashboard to see for all your team members to access and view all the preview environments and created along with the associated change.
Capability to control/limit the number of preview environments, discard events that are yet to be processed (this role is limited to DevOps and Admin members)
On-demand ability to go back to view logs, recreate any previous environment or even destroy any environment forever.
Ability to apply ad-hoc change and conduct what-if analysis on the ephemeral environments as well.

And finally, configure Configure just once and reap benefits forever

Simple onboarding steps for any application

...

Provide a GitHub token (GitLab and Bitbucket are in the roadmap)
Select Repository and branch (allows multiple repo)
Choose Git events that trigger “Roost Environment”
- Create PR
- Merge PR
- Create Tag

Specify Terraform Script/Repo for creating infrastructure resources outside of the cluster
AWS CloudFormation support is in the roadmap
You can specify optionally Terraform destroy steps as well for execution when the environment is shutdown

Specify Build tool for each repo
Choose the Build tool and build order (if it matters)
- Jenkins (Provide token to detect job-name, build status)
- Custom tools like Make, Maven, Apache Ant, Docker Build, BuildPacks

...