early-intern-9023810/08/2019, 2:00 PM
colossal-beach-4752710/08/2019, 3:32 PM
to a test instance, and have special
branches that deploy those environments as well. So “promoting builds to production” is just a matter of creating and merging a GitHub pull request. - We aren’t using GitHub’s Release features to tag builds, but instead create a separate release branch off of master. (This makes it easier to cherry-pick a patch or something if necessary, but it’s also kind of a pain.) - As far as cloud vs. dev machines, we put everything on app.pulumi.com. That makes it much easier to track resources and identify/reclaim stale stacks, etc. Developers update their dev stacks via script on their own machines, and aren’t hooked up to the automated CI/CD pipeline. (And each dev has their own dev-instances of stacks as desired.) Does that answer your questions? Happy to expand upon anything if it helps.
early-intern-9023810/08/2019, 5:25 PM