How do we ensure quality? How do we know the machine built the right product? We checked the inputs, what about the fabrication steps?Ĭonsider an automotive assembly operation (way overly simplified). In this use case, to a complex Ansible library used at a large customer.Ĭontinuing from last time ( ZNDP Episode 30), we discussed our specific purpose, along with the processes and tools to support it.
COMMANDS FOR CONQUER ONLINE PRIVATE SERVER SOFTWARE
CI provides immediate feedback as to any problems that arise.Ĭommonly associated with software development, but can be applied more generically. CI means merging code together regularly (daily) which kicks off a comprehensive set of tests to ensure code functionality and quality. This goes way past software development the “divide and conquer” approach for any complex project is best accomplished by continuous lateral communication. This is typically weeks or months as combining many silos of work is fraught with problems. Traditionally, developers would work in their own feature/topic branches for months, then deal with what is called “merge hell” towards the end of the project when entering the “integration testing” phrase. For today’s topic we are discussing CI/CD which is Continuous Integration / Continuous Delivery/Deployment. Nick Russo joins us once again for today’s topic of CI / CD … See Why?! Today we are picking up where Nick and I stopped in ZNDP Episode 30 – Designing for DevOps, if you didn’t get a chance to listen to that episode yet you can find it at zigbits.tech/30, If you need some context around DevOps you should definitely listen to Episode 30.
0 kommentar(er)
