Accelerating Open Source eCommerce Development with Preview Environments

Transcript

1. Accelerating Open Source eCommerce Development with Preview Environments X X
2. 2 About the author Hi, I’m Jacob Holistic Approach to Software Development Software Engineer @ Commerce Weavers Bunnyshell in Sylius adopter I had a short journey with Kubernetes/Helm charts/Rancher X X
3. 3 About the Commerce Weavers Core Team Members actively developing Sylius for past few years We provide development, mentoring and educational services around Sylius Services are available in convenient subscription plans X X
4. Pull Request life cycles
5. 5 Classical fl ow X X
6. 6 Classical fl ow characteristics X X Checking out the branch (especially after many QA <-> request changes) might be annoying and time consuming For example, you need to reserve a time block for QA Local environment might be a ff ecting the QA (e.g. your freshly checkout branch is miscon fi gured) We are sure the changes are working and they meet the requirements
7. 7 Usual Sylius fl ow X X
8. 8 Usual Sylius fl ow characteristics X X The PR is merged quicker We still need checkout branches manually, but we might delay it We are able to QA more PRs at once
9. 9 Sylius fl ow with using Bunnyshell X X
10. 10 Sylius fl ow with using Bunnyshell characteristics X X No need to change branches locally – easier to make an ad-hoc QA We are sure local environment issues are not a ff ecting QA, so no false-positive is reported The speed of QA is similar to the previous fl ow We merge working and high quality PR, so there’s is lower change to opening more PRs just to fi x minor issues
11. How Pull Request with Bunnyshell looks like?
12. 12 X X
13. 13 X X
14. 14 X X
15. 15 X X
16. 16 X X
17. How does it work?
18. 18 X X
19. 19 X X
20. 20 X X
21. 21 X X
22. 22 X X
23. 23 X X
24. Does Sylius use Bunnyshell only for preview environments?
25. Of course, not!
26. Bunnyshell hosts Sylius’ long-living developer preview environments ❤
27. 27 X X
28. 28 Bene fi ts X X Bunnyshell.yaml is way easier to use If anything is pushed to a branch, the environment is automatically redeployed We have features like easy connecting via SSH or remote development (who doesn’t like to debug on [almost] prod) Creating next environments is easy; just copy the already existing con fi guration, tweak few things; and… it works