filmov
tv
Intro to CI/CD Part 1: Getting Started with Docker | Digi-Key Electronics
Показать описание
Continuous Integration and Continuous Delivery (CI/CD) is the process of automating the testing and deployment of a software project. It is often used in large-scale, multi-person projects, but it can be useful in smaller projects and embedded firmware development. This tutorial shows you how to use Docker to create a simple image that automatically tests a program for the purposes of CI/CD.
CI/CD helps software teams automate testing, integration, and deployment to encourage small, rapid development changes to a project. By allowing developers to focus on creating practical, incremental improvements, less time is spent debugging larger issues that might arise, which means faster development with (ideally) fewer bugs. You’ll also sometimes see “Continuous Testing” (CT) included in CI/CD.
CI/CD frameworks can take many forms. One popular way to perform CI/CD is to use GitHub Actions (assuming you are using GitHub to host your projects). Actions can be configured to run every time a new commit is pushed or someone submits a pull request, and Actions are built using modular Docker images.
Docker is a virtualization platform that runs applications in instances known as “containers.” Containers are spawned from “images,” which are generated from a Dockerfile. A Dockerfile contains a set of instructions telling Docker how to create the image. Containers share common binaries and libraries as well as rely on the host OS drivers to work with the underlying hardware. While this approach reduces the isolation (and therefore reduces inherent security) found in virtual machines, it allows for much smaller guest images as well as incredibly fast boot and run times.
This video will walk you through the process of creating a Docker image that runs a simple Python script to compile and test a C program. We discuss how Docker plays an important role in CI/CD and demonstrate the process of creating an automated test.
Related Articles:
CI/CD helps software teams automate testing, integration, and deployment to encourage small, rapid development changes to a project. By allowing developers to focus on creating practical, incremental improvements, less time is spent debugging larger issues that might arise, which means faster development with (ideally) fewer bugs. You’ll also sometimes see “Continuous Testing” (CT) included in CI/CD.
CI/CD frameworks can take many forms. One popular way to perform CI/CD is to use GitHub Actions (assuming you are using GitHub to host your projects). Actions can be configured to run every time a new commit is pushed or someone submits a pull request, and Actions are built using modular Docker images.
Docker is a virtualization platform that runs applications in instances known as “containers.” Containers are spawned from “images,” which are generated from a Dockerfile. A Dockerfile contains a set of instructions telling Docker how to create the image. Containers share common binaries and libraries as well as rely on the host OS drivers to work with the underlying hardware. While this approach reduces the isolation (and therefore reduces inherent security) found in virtual machines, it allows for much smaller guest images as well as incredibly fast boot and run times.
This video will walk you through the process of creating a Docker image that runs a simple Python script to compile and test a C program. We discuss how Docker plays an important role in CI/CD and demonstrate the process of creating an automated test.
Related Articles:
Комментарии