docs/translations/ru-RU/content/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts.md

title, intro, product, redirect_from, versions

title	intro	product	redirect_from	versions
Persisting workflow data using artifacts	Artifacts allow you to share data between jobs in a workflow and store data once that workflow has completed.	{% data reusables.gated-features.actions %}	/articles/persisting-workflow-data-using-artifacts /github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts /actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts	free-pro-team enterprise-server * >=2.22

{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}

About workflow artifacts

Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. For pushes and pull requests, {% data variables.product.product_name %} stores artifacts for 90 days. The retention period for a pull request restarts each time someone pushes a new commit to the pull request.

These are some of the common artifacts that you can upload:

• Log files and core dumps
• Test results, failures, and screenshots
• Binary or compressed files
• Stress test performance output and code coverage results

{% if currentVersion == "free-pro-team@latest" %}

Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} For more information, see "Managing billing for {% data variables.product.prodname_actions %}."

{% else %}

Artifacts consume storage space on the external blob storage that is configured for {% data variables.product.prodname_actions %} on {% data variables.product.product_location %}.

{% endif %}

Artifacts are uploaded during a workflow run, and you can view an artifact's name and size in the UI. When an artifact is downloaded using the {% data variables.product.product_name %} UI, all files that were individually uploaded as part of the artifact get zipped together into a single file. This means that billing is calculated based on the size of the uploaded artifact and not the size of the zip file.

{% data variables.product.product_name %} provides two actions that you can use to upload and download build artifacts. For more information, see the {% if currentVersion == "free-pro-team@latest" %}actions/upload-artifact and download-artifact actions{% else %} actions/upload-artifact and download-artifact actions on {% data variables.product.product_location %}{% endif %}.

To share data between jobs:

• Uploading files: Give the uploaded file a name and upload the data before the job ends.
• Downloading files: You can only download artifacts that were uploaded during the same workflow run. When you download a file, you can reference it by name.

The steps of a job share the same environment on the runner machine, but run in their own individual processes. To pass data between steps in a job, you can use inputs and outputs. For more information about inputs and outputs, see "Metadata syntax for {% data variables.product.prodname_actions %}."

Passing data between jobs in a workflow

You can use the upload-artifact and download-artifact actions to share data between jobs in a workflow. This example workflow illustrates how to pass data between jobs in the same workflow. For more information, see the {% if currentVersion == "free-pro-team@latest" %}actions/upload-artifact and download-artifact actions{% else %} actions/upload-artifact and download-artifact actions on {% data variables.product.product_location %}{% endif %}.

Jobs that are dependent on a previous job's artifacts must wait for the dependent job to complete successfully. This workflow uses the needs keyword to ensure that job_1, job_2, and job_3 run sequentially. For example, job_2 requires job_1 using the needs: job_1 syntax.

Job 1 performs these steps:

• Performs a math calculation and saves the result to a text file called math-homework.txt.
• Uses the upload-artifact action to upload the math-homework.txt file with the name homework. The action places the file in a directory named homework.

Job 2 uses the result in the previous job:

• Downloads the homework artifact uploaded in the previous job. By default, the download-artifact action downloads artifacts to the workspace directory that the step is executing in. You can use the path input parameter to specify a different download directory.
• Reads the value in the homework/math-homework.txt file, performs a math calculation, and saves the result to math-homework.txt.
• Uploads the math-homework.txt file. This upload overwrites the previous upload because both of the uploads share the same name.

Job 3 displays the result uploaded in the previous job:

• Downloads the homework artifact.
• Prints the result of the math equation to the log.

The full math operation performed in this workflow example is (3 + 7) x 9 = 90.

name: Share data between jobs

on: [push]

jobs:
  job_1:
    name: Add 3 and 7
    runs-on: ubuntu-latest
    steps:
      - shell: bash
        run: |
          expr 3 + 7 > math-homework.txt
      - name: Upload math result for job 1
        uses: actions/upload-artifact@v2
        with:
          name: homework
          path: math-homework.txt

  job_2:
    name: Multiply by 9
    needs: job_1
    runs-on: windows-latest
    steps:
      - name: Download math result for job 1
        uses: actions/download-artifact@v2
        with:
          name: homework
      - shell: bash
        run: |
          value=`cat math-homework.txt`
          expr $value \* 9 > math-homework.txt
      - name: Upload math result for job 2
        uses: actions/upload-artifact@v2
        with:
          name: homework
          path: math-homework.txt

  job_3:
    name: Display results
    needs: job_2
    runs-on: macOS-latest
    steps:
      - name: Download math result for job 2
        uses: actions/download-artifact@v2
        with:
          name: homework
      - name: Print the final result
        shell: bash
        run: |
          value=`cat math-homework.txt`
          echo The result is $value

Sharing data between workflow runs

After a workflow ends, you can download a compressed file of the uploaded artifacts on {% data variables.product.product_name %} by finding the workflow run in the Actions tab. You can also use the {% data variables.product.prodname_dotcom %} REST API to download artifacts. For more information, see "Artifacts."

If you need to access artifacts from a previous workflow run, you can use the {% data variables.product.product_name %} REST API to retrieve artifacts. For more information, see "Get an artifact."

Uploading build and test artifacts

You can create a continuous integration (CI) workflow to build and test your code. For more information about using {% data variables.product.prodname_actions %} to perform CI, see "About continuous integration."

The output of building and testing your code often produces files you can use to debug test failures and production code that you can deploy. You can configure a workflow to build and test the code pushed to your repository and report a success or failure status. You can upload the build and test output to use for deployments, debugging failed tests or crashes, and viewing test suite coverage.

You can use the upload-artifact action to upload artifacts. When uploading an artifact, you can specify a single file or directory, or multiple files or directories. You can also exclude certain files or directories, and use wildcard patterns. We recommend that you provide a name for an artifact, but if no name is provided then artifact will be used as the default name. For more information on syntax, see the {% if currentVersion == "free-pro-team@latest" %}actions/upload-artifact action{% else %} actions/upload-artifact action on {% data variables.product.product_location %}{% endif %}.

Пример

For example, your repository or a web application might contain SASS and TypeScript files that you must convert to CSS and JavaScript. Assuming your build configuration outputs the compiled files in the dist directory, you would deploy the files in the dist directory to your web application server if all tests completed successfully.

|-- hello-world (repository)
|   └── dist
|   └── tests
|   └── src
|       └── sass/app.scss
|       └── app.ts
|   └── output
|       └── test
|   

This example shows you how to create a workflow for a Node.js project that builds the code in the src directory and runs the tests in the tests directory. You can assume that running npm test produces a code coverage report named code-coverage.html stored in the output/test/ directory.

The workflow uploads the production artifacts in the dist directory, but excludes any markdown files. It also and uploads the code-coverage.html report as another artifact.

name: Node CI

on: [push]

jobs:
  build_and_test:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@v2
      - name: npm install, build, and test
        run: |
          npm install
          npm run build --if-present
          npm test
      - name: Archive production artifacts
        uses: actions/upload-artifact@v2
        with:
          name: dist-without-markdown
          path: |
            dist
            !dist/**/*.md
      - name: Archive code coverage results
        uses: actions/upload-artifact@v2
        with:
          name: code-coverage-report
          path: output/test/code-coverage.html

Downloading or deleting artifacts

During a workflow run, you can download artifacts that were previously uploaded in the same workflow run. After a workflow run has been completed, you can download or delete artifacts on GitHub using the workflow run history.

Downloading artifacts during a workflow run

The actions/download-artifact action can be used to download previously uploaded artifacts during a workflow run.

{% note %}

Note: You can only download artifacts in a workflow that were uploaded during the same workflow run.

{% endnote %}

Specify an artifact's name to download an individual artifact. If you uploaded an artifact without specifying a name, the default name is artifact.

- name: Download a single artifact
  uses: actions/download-artifact@v2
  with:
    name: my-artifact

You can also download all artifacts in a workflow run by not specifying a name. This can be useful if you are working with lots of artifacts.

- name: Download all workflow run artifacts
  uses: actions/download-artifact@v2

If you download all a workflow run's artifacts, a directory for each artifact is created using its name.

For more information on syntax, see the {% if currentVersion == "free-pro-team@latest" %}actions/download-artifact action{% else %} actions/download-artifact action on {% data variables.product.product_location %}{% endif %}.

Downloading and deleting artifacts after a workflow run is complete

Artifacts automatically expire after 90 days, but you can always reclaim used {% data variables.product.prodname_actions %} storage by deleting artifacts before they expire on {% data variables.product.product_name %}.

{% warning %}

Warning: Once you delete an artifact, it can not be restored.

{% endwarning %}

{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %}

1. To download artifacts, use the Artifacts drop-down menu, and select the artifact you want to download.
2. To delete artifacts, use the Artifacts drop-down menu, and click {% octicon "trashcan" aria-label="The trashcan icon" %}.

{% if currentVersion == "free-pro-team@latest" %}

Дополнительная литература

• "Managing billing for {% data variables.product.prodname_actions %}".

{% endif %}