JOIN 2021 Testable and reusable build automation Using Tekton
- 1. 17/09/2021 TESTABLE AND REUSABLE BUILD AUTOMATION USING TEKTON Join 2021
- 2. 2 WHO AM I? o Consultant at Ordina as Cloud automation Engineer o Software architect & developer background o Interested in: Automation, public cloud in enterprises, hyperscale software o 30 years young, Koersel based o Company blog o LinkedIn
- 3. AGENDA o Build automation ● What is build automation? ● What is used? ● Why is it important? ● Why test? ● How to test? o Tekton ● What is Tekton? ● How does it work? ● What problem does it solve? ● Why should you use it? ● Tekton Setup o Recap
- 5. 5 WHAT IS BUILD AUTOMATION?
- 6. 6 WHAT IS COMMONLY USED?
- 7. o Consistent artefact creation o Offloading build processes from developer laptops o Ability to enable automated testing o Improve scalability of building applications o Repeatability of artefact creation o Continuous integration 7 WHY IS BUILD AUTOMATION IMPORTANT?
- 8. • Software like any other • It’s “just code” • Easier debugging • More consistent rollouts • Ease the development process • Knowing when a feature is “done”. Aka when all tests are green • Code/software quality 8 WHY TEST?
- 9. Unit tests • Validate business logic • Validate a build step • E.g. • Update environment file • Determine version number • Create unique name • Should be locally runnable • Doesn’t test • Integrations • External tooling • Validates output 9 HOW TO TEST? Integration tests • Validate that actions “tie together” correctly • Mocks integrations • Uses specific test input • E.g. • Image build • Validates • Side effects in other systems • Context passing between build steps • Outcome • Runnable in build system E2E tests • Validates complete pipeline • Uses real input • E.g. • Application build • Validates • Task execution • Order of task execution • Uses real integrations • Runnable in build system
- 11. “Tekton is a powerful and flexible open-source framework for creating CI/CD systems, allowing developers to build, test, and deploy across cloud providers and on-premise systems” 11 WHAT IS TEKTON? Source: https://tekton.dev/
- 12. o Framework o No out-of-the-box solution o Spin-off of Knative project o Backed by Google, IBM/Red Hat, Pivotal, … o Part of the CD Foundation o Core to Jenkins X, Core to OpenShift pipelines o Multiple subprojects o Dashboard o Triggers o Pipelines o … o Runs on top of Kubernetes 12 WHAT IS TEKTON?
- 13. None 13 WHAT PROBLEM DOES TEKTON SOLVE?
- 14. o Great building block for tailor fit solution o Highly configurable/customizable o Highly scalable (*) o Kubernetes native o Component definition o “The right ingredient to make a fantastic meal” 14 WHY SHOULD I USE IT?
- 15. Pipeline • Set of tasks • Executed in order • Optionally in parallel • Defined as a single component • Kubernetes Custom resources • Used group a set of tasks which produce an artefact E.g.: Application build Step • Smallest execution component • Kubernetes Container • Container image + command • Runs until completion • Part of Task definition E.g.: Maven test Task • Set of steps • Executed in order • Defined as a single component • Kubernetes Custom resources • Kubernetes Pod • Used a logical set of steps which only make sense if executed together E.g.: Maven build 15 HOW DOES IT WORK? Terminology Source: https://tekton.dev/docs/concepts/
- 16. Trigger • External events • Webhook • Can trigger a pipeline • Filtering • Kubernetes Custom resources • Trigger • TriggerTemplate TaskRun • Actual execution of a task • Directly connected to a pod • Copies pod template from task and runs it • Kubernetes Custom resource PipelineRun • Actual execution of a pipeline • Copies pipeline definition and creates tasks • Monitors tasks execution to trigger new ones if needed • Kubernetes Custom resource 16 HOW DOES IT WORK? Terminology Source: https://tekton.dev/docs/concepts/
- 17. 17 HOW DOES IT WORK? Terminology Controllers • Tekton controllers execute control loops • Eventually consistent • Reconcile state in cluster to resources defined in cluster Source: https://tekton.dev/docs/concepts/ Workspace • A work folder • Share data between tasks • Connected to a single pipeline • Mapped to Persistent Volume Claim in Kubernetes • Part of task and pipeline definitions
- 18. 18 WORKFLOW
- 19. 19 WORKFLOW
- 20. 20 WORKFLOW
- 21. 21 WORKFLOW
- 22. 22 WORKFLOW
- 23. 23 WORKFLOW
- 24. 24 WORKFLOW
- 25. Unit tests • Execute a single Tekton step • Validate output • Setup • Only use scripts in “step” • Standard testing (Python, Bash, Java, …) 25 TESTING Integration tests • Execute single Tekton task • Validate execution • Validate side effects • Custom pipeline • Setup • Use pre-task to setup context • Use post-task to perform validations E2E tests • Execute Tekton pipeline • Using real world input • Optionally forked to prevent naming conflicts • Setup • Have test pipeline create another pipeline • Validate output based on Tekton pipelineRun
- 26. • Treat pipelines as regular code • Versioning • Automated testing • Release cycle • Move build system close to application landscape • Makes test integration easier • Adopt opensource tooling, even in corporate environment • Tip: Tekline, Renovate bot • Use tooling to assist in adoption 26 LESSONS LEARNED
- 27. Pieter Vincken Cloud Automation Engineer Competence Lead: Code2Cloud E [email protected]