From the course: GitHub Actions for CI/CD

Unlock the full course today

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

Delivering software artifacts and packages

Delivering software artifacts and packages - GitHub Tutorial

From the course: GitHub Actions for CI/CD

Start my 1-month free trial Buy for my team

Delivering software artifacts and packages

“

- [Instructor] After code has been integrated and tested, it can be used to create an artifact. When we automate artifact creation we can refer to it as continuous delivery. On every push to a code repository, continuous integration combines the new code with the existing code and runs tests. This can include linting, static analysis and unit tests. After integration is complete, continuous delivery builds the code into an artifact that can be used as part of a solution. This artifact is referred to as a package. Continuous delivery places the package in a location where it can be retrieved for use later. We'll also refer to the place where the package is stored as a registry. Once the package is stored in the registry, a deployable version of the software is available and ready to go. Each programming language has their very own package format and registry. Java creates JAR files and uses the Apache Maven or Gradle…

Contents