3 ms·

There are times when some corner of software development speaks a specialized language and this is an example. 1. Conveyor belt(?) of environments. Hydrate(?)

There are times when some corner of software development speaks a specialized language and this is an example. 1. Conveyor belt(?) of environments. Hydrate(?) the env(ironment). Mask(?) from prod(uction) 2. I think I got this. Typical "merge to main pipeline" with built product and test results as outputs. DevEx(?). And not sure why I wouldn't see pipeline #4 in my build loop because I can't deploy unless 2, 3 and 4 pass.... Maybe you mean I don't wait to see it. Also not sure how it's faster because environments still need to be brought up. Unless you are trying to say that the environment is already running when the merge to master pipeline succeeds.

jen20 5y ago
> Unless you are trying to say that the environment is already running when the merge to master pipeline succeeds. I read this as implying that there would be a "warm pool" of environments ready to go at any given time. This is an approach I've used in the past when environment construction was expensive (e.g. Windows servers), but there are certainly tradeoffs.
CraigJPerry 5y ago
Ahh :-) >> Conveyor belt Not a technical term, i just meant a repeatable stream of environments being created >> Hydrate This one is a pretty common term, if you hydrate a schema then you just populate it with data >> Mask In many industries (health, finance, even more since GDPR and the ilk) production data can be sensitive, it might have Personally Identifiable Information for example. Masking is the process of taking a value from production and obscuring it but with plausible-looking data. It can be time consuming and gnarly. >> DevEx Developer Experience - usually i say DX but i stopped myself on that one when i was writing the comment! >> not sure why I wouldn't see pipeline #4 in my build loop It's part of your deployment loop for sure, but there's no reason it has to be part of your inner dev loop. You can continue on with your next task and be confident you'll start receiving telemetry from prod for your new feature's behaviour soon. >> Unless you are trying to say that the environment is already running when the merge to master pipeline succeeds Exactly this. The time for creating that env was spent async outside of your inner dev loop.

jen20 5y ago

> Unless you are trying to say that the environment is already running when the merge to master pipeline succeeds. I read this as implying that there would be a "warm pool" of environments ready to go at any given time. This is an approach I've used in the past when environment construction was expensive (e.g. Windows servers), but there are certainly tradeoffs.

CraigJPerry 5y ago

Ahh :-) >> Conveyor belt Not a technical term, i just meant a repeatable stream of environments being created >> Hydrate This one is a pretty common term, if you hydrate a schema then you just populate it with data >> Mask In many industries (health, finance, even more since GDPR and the ilk) production data can be sensitive, it might have Personally Identifiable Information for example. Masking is the process of taking a value from production and obscuring it but with plausible-looking data. It can be time consuming and gnarly. >> DevEx Developer Experience - usually i say DX but i stopped myself on that one when i was writing the comment! >> not sure why I wouldn't see pipeline #4 in my build loop It's part of your deployment loop for sure, but there's no reason it has to be part of your inner dev loop. You can continue on with your next task and be confident you'll start receiving telemetry from prod for your new feature's behaviour soon. >> Unless you are trying to say that the environment is already running when the merge to master pipeline succeeds Exactly this. The time for creating that env was spent async outside of your inner dev loop.