Never ask who is using staging again - Introducing Divergence
layervault.tumblr.com
Never ask who is using staging again - Introducing Divergence
1–10 of 10 posts
Re: Never ask who is using staging again - Introducing Divergence
#2Wow, I want this at work.
Re: Never ask who is using staging again - Introducing Divergence
#3Wow, I want this at work.
I'd imagine that it's a QA engineer's dream. Imagine never having to worry about spinning up some brach to test. That's kinda cool.
Re: Never ask who is using staging again - Introducing Divergence
#4This looks amazing. We've got a few QA servers, but still run into the same problem.
Re: Never ask who is using staging again - Introducing Divergence
#5Wow, this is pretty awesome. We run into this issue all the time. Mainly using staging for an external demo, but needing to deploy production updates before the branch on staging is ready to go live. Great work LayerVault!
Re: Never ask who is using staging again - Introducing Divergence
#6I definitely have to try it!
How do you handle migrations? What if there is a migration in the feature-1 branch which breaks other branches?
Re: Never ask who is using staging again - Introducing Divergence
#7what happens with changes that have impact on the datastore such as adding migrations? Do those get executed when the appropriate branch gets checked out? What happens when two branches create conflicting changes in the datastore?
Re: Never ask who is using staging again - Introducing Divergence
#8what happens with changes that have impact on the datastore such as adding migrations? Do those get executed when the appropriate branch gets checked out? What happens when two branches create conflicting changes in the datastore?
At LayerVault, each migration always happens on its own branch separate from the feature. We've been operating like that since day 1, and it hasn't been an issue yet.
Re: Never ask who is using staging again - Introducing Divergence
#9Does it support subdomains?
aaa.staging1.example.com api.staging2.example.com
Re: Never ask who is using staging again - Introducing Divergence
#10what happens with changes that have impact on the datastore such as adding migrations? Do those get executed when the appropriate branch gets checked out? What happens when two branches create conflicting changes in the datastore?
At LayerVault, each migration always happens on its own branch separate from the feature. We've been operating like that since day 1, and it hasn't been an issue yet.
That's really interesting. Have you or someone else written up that workflow?