CircleCi - Artifacts




Using Artifacts

-Artifacts persist data after a job is completed  and may be used for longer-term storage of your build process.
-If a job produces persistent artifacts such as screenshots, coverage reports, core files, or deployment tarballs, CircleCi can automatically save and link them for you.
-Other examples of Artifacts are:
  *A .jar file as the output of Java build/test process.
  *A project that is packaged as an Android app where the .apk file is uploaded to Google Play



Uploading artifacts

  working_directory: /tmp
  steps:
    - run:
        name: Creating Dummy Artifacts
        command:
          echo "my artifact file" > /tmp/artifact-1;
          mkdir /tmp/artifacts;
          echo "my artifact files in a dir" > /tmp/artifacts/artifact-2;
    - store_artifacts::
        path: /tmp/artifact-1

        destination: artifact-file

    - store_artifacts::
        path: /tmp/artifacts


Artifacts tab



Artifact Storage

-Artifacts are stored on Amazon S3
-We don't make guarantees about how long artifacts are available for.
-If you're relying on them as a source of decomunetation / persistent content, we recommend deploying the output target.

An example of artifacts in CircleCI






Komentarze

Popularne posty z tego bloga

Kubernetes

Helm

Ansible Tower / AWX