Optmizing workflows with Circle CI (v2)

--- same content of v1 but different presentation ---
CircleCI is a powerful tool that helps us to manage a continuous integration and delivery for our projects. It's common developers create a hard and solid workflow where some important features aren't used. Let's learn some techniques to improve the time of execution with caching, workplaces and reusable steps.

Transcript

1. C Optimizing workflows With CircleCI
2. • What's CircleCI and Concepts • Common mistakes • Use case
3. Rurik Pinheiro Full stack Developer at Cheesecake Labs • 7 years building Web applications • Continuous integrations • Python (but PHP, C# and Javascript) rurikspin@gmail.com Rurik Pinheiro
4. What is CircleCI CircleCI automates your software builds, tests, and deployments. It's a powerful tool to build continuous and delivery integration (CI/CD).
5. CONTINUOUS INTEGRATION It is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early. CONTINUOUS DELIVERY It is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time and, when releasing the software.
6. Continuous Integration Build Test style
7. Continuous Delivery
8. Alternatives
9. How does it work?
10. CONFIG.YML
11. What do I need to know? A workflow is a set of rules for defining a collection of jobs and their run order. Workflows support complex job orchestration using a simple set of configuration keys to help you resolve failures sooner. Workflow Steps are a collection of executable commands which are run during a job Steps Jobs are a collection of Steps. All of the steps in the job are executed in a single unit which consumes a CircleCI container from your plan while it’s running. Jobs
12. A workflow
13. 13 Show me the code
14. Common issues Let's understand problems relate to performance, scalability and maintainability
15. Issue #1: Mono job
16. Issue #1: Mono job
17. QUEUED RUNNING SUCCESS FAIL
18. QUEUED RUNNING SUCCESS FAIL
19. QUEUED RUNNING SUCCESS FAIL
20. QUEUED RUNNING SUCCESS FAIL
21. QUEUED RUNNING SUCCESS FAIL
22. QUEUED RUNNING SUCCESS FAIL
23. QUEUED RUNNING SUCCESS FAIL
24. QUEUED RUNNING SUCCESS FAIL
25. QUEUED RUNNING SUCCESS FAIL
26. Issue #1: Mono job TIME CONTAINERS ($$$)
27. 27 Show me the code
28. Issue #2: no caching
29. 29 Show me the code
30. Issue #3: no workspace TESTING CODE ANALYSIS WORKFLOW
31. 31 Just show me
33. References https://circleci.com/docs/ https://www.thoughtworks.com/continuous-integration https://continuousdelivery.com/ https://github.com/rurikhero/cloudtalks-circleci-sample https://circleci.com/gh/rurikhero/workflows/cloudtalks-circleci- sample
34. Thank you Does anyone have any questions? rurikspin@gmail.com github.com/rurikhero