artifact
A file produced by a build, such as a compiled program or an image, that is stored and passed on to later steps.
In more detail
Artifacts are usually versioned and kept, so a later step, or a later investigation, can use exactly the same file. Building once and promoting that same artifact through testing and release makes releases traceable.
Examples
Build once, give the artifact an identity such as a version and a digest, and promote those same bytes from test to staging to production. Configuration enters at deploy time, not in the artifact.the healthcheck binary is the release artifacttarget/inventory-1.0.0.jarThe course promotes one tested container image.In Terraform: In a Terraform pipeline the saved plan file is the key artifact: produced by the plan job, reviewed, then applied exactly by a later job. Store it as carefully as state, because it can contain secrets.Related terms
- job resource — A resource that represents long-running work, answered with 202 Accepted and a Location the client can poll for progress and the result.
- artifact promotion — Moving the exact artifact that passed testing on to the next environment, instead of building it again.
- digest — A SHA-256 hash of an image's manifest that identifies its exact content and can never be moved to other bytes.
- immutable — Something that cannot be changed after it is created; to change it you make a new one.
- build — The automated step that turns source code into something runnable, and the result of that step.
- upload-artifact action — The official action that uploads files from a job to artifact storage under a name, so later jobs or people can download them.
- download-artifact action — The official action that downloads an artifact uploaded earlier in the same workflow run, by name, into the job's workspace.
- retention period — How long stored data such as a workflow artifact is kept before it is deleted automatically.
- dependency cache — Saved copies of downloaded dependencies that GitHub Actions restores into later runs so they need not be fetched again.
- image promotion — Moving the exact same, already-tested image through environments, such as staging to production, without rebuilding it.
- image — A read-only package containing a program and everything it needs to run, used as the template for containers.
- build cache — Saved results of earlier build steps that a build tool, such as Docker, reuses when nothing a step depends on has changed.
- remote caching — Storing build outputs on a shared server so that any developer or CI machine with the same inputs can download the result instead of rebuilding.
- multi-stage build — A Dockerfile with several FROM stages, where later stages copy only what they need from earlier ones.
- JAR file — A zip archive holding compiled classes and resources, plus a manifest describing them, which the JVM can load directly.
- digital signature — A value computed from data and a secret key that lets anyone with the matching verification key confirm the data came from the key holder and was not changed.
- SBOM — A list of every software package and version inside an image, like an ingredients label.
- saved plan — A plan written to a file with -out, which terraform apply can later carry out exactly as reviewed.
- pipeline — An automated sequence of steps, such as build, test, scan and publish, that runs on every change.
Taught in
- Large Payloads And Streaming — Modern API Architecture: REST, GraphQL & gRPC
- CodePipeline: Stages, Actions And The Key Nobody Shared — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- CodeBuild: The Build That Passed With Failing Tests — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Artifacts: Where Packages And Images Live, And Die — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Pipeline Security: The Build Role That Could Do Anything — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Long-Stem Clinic: When Two Answers Both Work — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- What Argo Workflows Runs: Controller, Server And One Pod A Step — Certified Argo Project Associate (CAPA) Exam Prep
- Artifacts: Files That Outlive The Pod — Certified Argo Project Associate (CAPA) Exam Prep
- Data Processing Jobs And CronWorkflows — Certified Argo Project Associate (CAPA) Exam Prep
- Final Mock, Review And A Trap Sprint — Certified Argo Project Associate (CAPA) Exam Prep
- What Is a Pipeline? — Continuous Integration & Continuous Delivery Pipelines
- Passing Data Between Jobs: Artifacts — Continuous Integration & Continuous Delivery Pipelines
- Artifact Promotion: Staging to Production — Continuous Integration & Continuous Delivery Pipelines
- Ten Percent Off For Everyone: Source Control And Pipelines — CompTIA Cloud+ (CV0-004) Exam Prep
- DevOps Sprint: Tax At A Hundred Percent — CompTIA Cloud+ (CV0-004) Exam Prep
- Sixty Six Of Eighty Five: The Mock And Its Report — CompTIA Cloud+ (CV0-004) Exam Prep
- Config And Backing Services — DevOps & Site Reliability Engineering
- Build, Release, Run And Processes — DevOps & Site Reliability Engineering
- Continuous Integration — DevOps & Site Reliability Engineering
- Building And Versioning The Artifact — DevOps & Site Reliability Engineering
- Containers And Orchestration Context — DevOps & Site Reliability Engineering
- Pipelines And GitOps Context — DevOps & Site Reliability Engineering
- Build, Test And Promote The Same Image In CI — Docker Architecture & Production Containers
- From Local Containers To Kubernetes — Docker Architecture & Production Containers
- Solutions, Projects, and Target Frameworks — Modern .NET Core, C# & Enterprise Microservices
- OpenTelemetry, Container Publishing and Trimming — Modern .NET Core, C# & Enterprise Microservices
- Monorepo Architecture: Workspaces & Turborepo — Production Full-Stack Engineering
- Unified Build Pipelines: Caching & Dependency Graphs — Production Full-Stack Engineering
- Containerization Architecture: Multi-Stage Dockerfiles — Production Full-Stack Engineering
- How The Exam Works: Fifty Questions, No Notes — GitLab Certified CI/CD Associate Exam Prep
- Continuous Integration, Delivery And Deployment: One Keyword Apart — GitLab Certified CI/CD Associate Exam Prep
- From Push To Runner: How GitLab Starts A Pipeline — GitLab Certified CI/CD Associate Exam Prep
- Anatomy Of .gitlab-ci.yml, And Three Ways To Check It — GitLab Certified CI/CD Associate Exam Prep
- Stages Versus Needs: Building The Pipeline As A Graph — GitLab Certified CI/CD Associate Exam Prep
- Parent, Child And Multi-Project Pipelines — GitLab Certified CI/CD Associate Exam Prep
- Artifacts: Which Files Reach Which Jobs — GitLab Certified CI/CD Associate Exam Prep
- Caching: Dependencies That Survive Between Pipelines — GitLab Certified CI/CD Associate Exam Prep
- Environments, Review Apps And Deployments — GitLab Certified CI/CD Associate Exam Prep
- The Container Registry: Build, Tag, Push, Clean Up — GitLab Certified CI/CD Associate Exam Prep
- Adding GitLab's Security Scanners To A Pipeline — GitLab Certified CI/CD Associate Exam Prep
- Debugging Pipelines: The Graph, The Errors, The Logs — GitLab Certified CI/CD Associate Exam Prep
- Faster Pipelines: Minutes You Can Win Back — GitLab Certified CI/CD Associate Exam Prep
- Pipeline Clinic: Five Tickets, Five Fixes — GitLab Certified CI/CD Associate Exam Prep
- Final Mock And Review: One Question Short — GitLab Certified CI/CD Associate Exam Prep
- Building Static Binaries — Concurrent Systems Programming with Go
- Exporting Results as JSON — Concurrent Systems Programming with Go
- Containerizing and Testing the Final Build — Concurrent Systems Programming with Go
- The Virtual Machine, The Kit And The Runtime — Modern Java: Virtual Threads & High-Throughput Services
- Packaging Into A Container — Modern Java: Virtual Threads & High-Throughput Services
- Tying It All Together — Modern Java: Virtual Threads & High-Throughput Services
- The Environment Variable Trap — Application Security & Threat Modeling for Engineers
- Lockfiles And Reproducible Builds — Application Security & Threat Modeling for Engineers
- Software Bill Of Materials — Application Security & Threat Modeling for Engineers
- Provenance And Signing — Application Security & Threat Modeling for Engineers
- How To Stop Drowning In Findings — Application Security & Threat Modeling for Engineers
- Predicting Changes, Then Applying Them — Infrastructure as Code with Terraform
- Running Terraform In CI — Infrastructure as Code with Terraform
- Native Testing With Tftest Files — Infrastructure as Code with Terraform
- Provider Mocking For Tests — Infrastructure as Code with Terraform
- Policy As Code With OPA — Infrastructure as Code with Terraform
- Releasing The Real Cloud Artifact — Infrastructure as Code with Terraform
References
- Google AIP-151: Long-running operations
- NIST glossary: artifact
- Docker Build: continuous integration
- GitHub Docs: Workflow artifacts
- actions/upload-artifact on GitHub
- Turborepo: Configuring tasks (outputs)
- Apache Maven: POM Reference
- SLSA: terminology
- Running Terraform in automation