Skip to main content

[Step] Artifact

Overview​

Artifacts are files or sets of files generated during a pipeline execution that you can save after a job finishes. They allow you to preserve data like build outputs or test results beyond the job's lifespan.

Common examples of artifacts include:

  • Test reports, error logs, and screenshots
  • Compiled binaries or archives
  • Code coverage reports

Artifacts get uploaded while a workflow is running. You can see their names and sizes in the user interface.

Artifacts list displayed in the HexDroid UI

Syntax​

steps:
  artifact:
    # A file or directory with a wildcard pattern that describes what to upload
    # Required.
    paths:
      - "app/build/libs/app.jar"   # Exact file match
      - "*/*.jar"                  # Match .jar files in all subdirectories
      - "*/build/*.jar"            # Match .jar files in build folders

Artifact grouping​

When artifact step used from within the aosp step all uploads will have a common parent based lunch target, so finding artifacts belonging to a given lunch target is easier!

Artifacts list grouped by AOSP lunch target