From the course: Learning GitHub Actions: Event-Driven Automation for Your Codebase

Unlock this course with a free trial

Join today to access over 24,900 courses taught by industry experts.

Building and managing artifacts

Building and managing artifacts - GitHub Tutorial

From the course: Learning GitHub Actions: Event-Driven Automation for Your Codebase

Start my 1-month free trial Buy for my team

Building and managing artifacts

“

- [Instructor] After linting and testing our code, the next stage in the pipeline builds and manages artifacts. The purpose of the build stage is to compile a project's code and dependencies into some sort of binary package. Binary simply means that the project's code has been transformed from a text representation into some sort of machine-readable format. For example, a C++ project would use the new C compiler to compile code into executables. A build step that creates archives could use tools like Zip, Tar, or Jar to collect groups of files into a Zip file, tarball or Java archive. And in our case, we'll be using Docker as a build tool to create file system layers that become a container image. These binaries, archives and images are known as artifacts. Artifacts are intended to exist beyond the life of the build process, making the compile code portable and easier to use. Artifacts are often stored and distributed from package registries. Not only do registries provide storage and…

Contents