Optmizing workflows with Circle CI

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. with optimizing workflows
2. All concepts were applied in a real project Knows how to find me Understand a little more about workflows, steps and jobs Explain what's this tool and CI/CD concepts References and attachments Let's talk about caching, reusable steps and more 01 05 03 02 06 04 About ME A real use case How does it work LEARN MORE Common issues What's circleci
3. About me
4. CircleCI automates your software builds, tests, and deployments. It's a powerful tool to build continuous and delivery integration (CI/CD). What's CIRCLECI
5. 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, concepts Continuous integration
6. Continuous integration • Build docker images • Run tests • Check Code 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. Talk is cheap, show me the code
14. Let's understand problems relate to performance, scalability and maintainability COMMON ISSUES
15. ISSUE NUMBER #1: monojob
16. QUEUED RUNNING SUCCESS FAIL
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. ISSUE NUMBER #1: monojob TIME CONTAINERS ($$$)
26. Talk is cheap, show me the code
27. ISSUE NUMBER #2: no caching
28. Talk is cheap, show me the code
29. ISSUE NUMBER #3: no workspace TESTING CODE ANALYSIS WORKFLOW
30. Talk is cheap, show me the code
33. 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 References
34. CREDITS: This presentation template was created by Slidesgo, including icons by Flaticon, and infographics & images by Freepik. THANKS Does anyone have any questions? rurikspin@gmail.com github.com/rurikhero linkedin.com/in/rurik-pinheiro-58b2b2119 Follow the projects