Re:Run end-to-end tests faster with Firecracker
by CraigJPerry on Monday April 18, 2022 @04:27PM
(#31076038)
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.
>> 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.