[zackkitzmiller]

This was a constant pain point for us as the engineering team grew. With a single staging environment, we could only have one changeset tested at a time. We built a tool like this internally and the engineers love it. When you have 20 feature going out in a week, it's not reasonable to have to wait for staging or qa to be available. We happened to call this 'review apps' but it's based on a similar principle. You can specify in the deployment tool which service you'd like to deploy as a review app, and a PR number.

This is incredibly useful with many interconnected codebases have related changes (I know, bad SoA. best practices are hard). Then I can point review-3918.SERVICENAME.service.XXX.stag's connection string to review-1111.SERVICENAME.service.XXX.stag to ensure that everything is working as expected.

[emilsoman]

We would love to interview you to understand your experience, can you please drop me a mail here: [e-mail]? Btw, we had the exact same requirement too - be able to test how a related change in multiple apps would affect the whole system. Check out our deployment form that helps us do this now: https://user-images.githubusercontent.com/1707078/53836663-6...