How to Upload Yml File in Github
Upload-Artifact v3
This uploads artifacts from your workflow allowing you to share data between jobs and shop data once a workflow is complete.
See also download-antiquity.
What'southward new
- Easier upload
- Specify a wildcard pattern
- Specify an individual file
- Specify a directory (previously you were limited to only this option)
- Multi path upload
- Use a combination of individual files, wildcards or directories
- Support for excluding certain files
- Upload an artifact without providing a proper noun
- Fix for artifact uploads sometimes not working with containers
- Proxy back up out of the box
- Port entire action to typescript from a runner plugin and then it is easier to collaborate and accept contributions
Refer here for the previous version
Usage
See action.yml
Upload an Individual File
steps: - uses: actions/checkout@v2 - run: mkdir -p path/to/artifact - run: echo howdy > path/to/artifact/world.txt - uses: actions/upload-artifact@v3 with: name: my-antiquity path: path/to/artifact/world.txt Upload an Entire Directory
- uses: deportment/upload-artifact@v3 with: name: my-antiquity path: path/to/artifact/ # or path/to/artifact Upload using a Wildcard Pattern
- uses: actions/upload-artifact@v3 with: proper name: my-artifact path: path/**/[abc]rtifac?/* Upload using Multiple Paths and Exclusions
- uses: actions/upload-artifact@v3 with: name: my-artifact path: | path/output/bin/ path/output/test-results !path/**/*.tmp For supported wildcards along with behavior and documentation, see @deportment/glob which is used internally to search for files.
If a wildcard pattern is used, the path hierarchy volition be preserved after the first wildcard pattern:
path/to/*/directory/foo?.txt => ∟ path/to/some/directory/foo1.txt ∟ path/to/some/directory/foo2.txt ∟ path/to/other/directory/foo1.txt would exist flattened and uploaded as => ∟ some/directory/foo1.txt ∟ some/directory/foo2.txt ∟ other/directory/foo1.txt If multiple paths are provided every bit input, the least mutual antecedent of all the search paths will be used equally the root directory of the artifact. Exclude paths do not bear on the directory construction.
Relative and absolute file paths are both allowed. Relative paths are rooted against the current working directory. Paths that brainstorm with a wildcard character should be quoted to avoid existence interpreted as YAML aliases.
The @deportment/antiquity package is used internally to handle well-nigh of the logic effectually uploading an artifact. In that location is extra documentation around upload limitations and behavior in the toolkit repo that is worth checking out.
Customization if no files are establish
If a path (or paths), upshot in no files existence institute for the antiquity, the activity will succeed but print out a alarm. In certain scenarios it may be desirable to fail the activity or suppress the alarm. The if-no-files-found option allows you to customize the behavior of the action if no files are found:
- uses: actions/upload-antiquity@v3 with: name: my-artifact path: path/to/artifact/ if-no-files-found: error # 'warn' or 'ignore' are likewise available, defaults to `warn` Conditional Artifact Upload
To upload artifacts only when the previous step of a chore failed, use if: failure():
- uses: deportment/upload-antiquity@v3 if: failure() with: proper noun: my-artifact path: path/to/artifact/ Uploading without an artifact proper name
You lot tin upload an artifact without specifying a name
- uses: actions/upload-artifact@v3 with: path: path/to/artifact/world.txt If not provided, artifact will be used every bit the default name which will manifest itself in the UI after upload.
Uploading to the same artifact
With the following example, the available artifact (named artifact past default if no name is provided) would contain both earth.txt (hullo) and actress-file.txt (howdy):
- run: echo hi > world.txt - uses: deportment/upload-artifact@v3 with: path: earth.txt - run: echo hullo > actress-file.txt - uses: actions/upload-artifact@v3 with: path: actress-file.txt - run: echo hello > earth.txt - uses: actions/upload-artifact@v3 with: path: globe.txt Each antiquity behaves as a file share. Uploading to the aforementioned antiquity multiple times in the same workflow can overwrite and append already uploaded files:
strategy: matrix: node-version: [8.x, ten.ten, 12.ten, 13.x] steps: - proper name: Create a file run: echo ${{ matrix.node-version }} > my_file.txt - proper noun: Accidentally upload to the aforementioned artifact via multiple jobs uses: actions/upload-artifact@v3 with: proper name: my-artifact path: ${{ github.workspace }} Warning: Exist careful when uploading to the same antiquity via multiple jobs as artifacts may become corrupted. When uploading a file with an identical proper name and path in multiple jobs, uploads may neglect with 503 errors due to alien uploads happening at the same time. Ensure uploads to identical locations to not interfere with each other.
In the in a higher place example, four jobs will upload iv different files to the same antiquity only there volition just be one file available when my-antiquity is downloaded. Each job overwrites what was previously uploaded. To ensure that jobs don't overwrite existing artifacts, use a different proper noun per job:
uses: actions/upload-antiquity@v3 with: name: my-antiquity ${{ matrix.node-version }} path: ${{ github.workspace }} Environment Variables and Tilde Expansion
You lot tin use ~ in the path input every bit a substitute for $HOME. Basic tilde expansion is supported:
- run: | mkdir -p ~/new/artifact echo hello > ~/new/artifact/world.txt - uses: deportment/upload-artifact@v3 with: proper name: Artifacts-V3 path: ~/new/**/* Surround variables along with context expressions can also be used for input. For documentation see context and expression syntax:
env: name: my-artifact steps: - run: | mkdir -p ${{ github.workspace }}/artifact repeat hi > ${{ github.workspace }}/antiquity/world.txt - uses: actions/upload-antiquity@v3 with: name: ${{ env.name }}-name path: ${{ github.workspace }}/artifact/**/* For surroundings variables created in other steps, make sure to employ the env expression syntax
steps: - run: | mkdir testing echo "This is a file to upload" > testing/file.txt echo "artifactPath=testing/file.txt" >> $GITHUB_ENV - uses: actions/upload-antiquity@v3 with: proper noun: antiquity path: ${{ env.artifactPath }} # this will resolve to testing/file.txt at runtime Retention Period
Artifacts are retained for 90 days past default. You tin can specify a shorter memory menstruation using the retention-days input:
- name: Create a file run: echo "I won't live long" > my_file.txt - proper noun: Upload Antiquity uses: deportment/upload-artifact@v3 with: name: my-artifact path: my_file.txt retention-days: 5 The retention menstruum must be betwixt 1 and ninety inclusive. For more information see antiquity and log retention policies.
Where does the upload go?
At the bottom of the workflow summary page, at that place is a dedicated section for artifacts. Here's a screenshot of something yous might encounter:
There is a trashcan icon that tin be used to delete the antiquity. This icon will only appear for users who have write permissions to the repository.
The size of the antiquity is denoted in bytes. The displayed artifact size denotes the raw uploaded artifact size (the sum of all the individual files uploaded during the workflow run for the antiquity), not the compressed size. When you click to download an artifact from the summary folio, a compressed nada is created with all the contents of the artifact and the size of the zip that y'all download may differ significantly from the displayed size. Billing is based on the raw uploaded size and non the size of the zip.
Limitations
Zipped Artifact Downloads
During a workflow run, files are uploaded and downloaded individually using the upload-artifact and download-artifact deportment. Notwithstanding, when a workflow run finishes and an artifact is downloaded from either the UI or through the download api, a nada is dynamically created with all the file contents that were uploaded. In that location is currently no fashion to download artifacts later on a workflow run finishes in a format other than a zip or to download artifact contents individually. One of the consequences of this limitation is that if a zip is uploaded during a workflow run and then downloaded from the UI, at that place will be a double zip created.
Permission Loss
chmod and then upload that file, postal service-download the file is no longer guaranteed to be set as an executable.
Case Insensitive Uploads
A.txt and a.txt with the same root path, only a single file volition exist saved and bachelor during download.
Maintaining file permissions and example sensitive files
If file permissions and case sensitivity are required, you lot can tar all of your files together before artifact upload. Post download, the tar file will maintain file permissions and case sensitivity:
- proper name: Tar files run: tar -cvf my_files.tar /path/to/my/directory - name: Upload Antiquity uses: actions/upload-antiquity@v3 with: name: my-antiquity path: my_files.tar As well many uploads resulting in 429 responses
A very minute subset of users who upload a very very big amount of artifacts in a short menses of time may see their uploads throttled or fail considering of Asking was blocked due to exceeding usage of resource 'DBCPU' in namespace or Unable to copy file to server StatusCode=TooManyRequests.
To reduce the run a risk of this happening, you tin can reduce the number of HTTP calls fabricated during artifact upload by zipping or archiving the contents of your antiquity before an upload starts. Equally an example, imagine an antiquity with 1000 files (each 10 Kb in size). Without any modification, there would be effectually thou HTTP calls made to upload the artifact. If you lot zip or archive the artifact beforehand, the number of HTTP calls can be dropped to single digit territory. Measures like this volition significantly speed upwards your upload and prevent uploads from being throttled or in some cases fail.
Additional Documentation
See Storing workflow data every bit artifacts for additional examples and tips.
See extra documentation for the @deportment/artifact package that is used internally regarding certain behaviors and limitations.
License
The scripts and documentation in this projection are released nether the MIT License.
Source: https://github.com/actions/upload-artifact
Postar um comentário for "How to Upload Yml File in Github"