You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/pipelines/artifacts/pipeline-artifacts.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ Packages in Azure Artifacts are immutable. Once you publish a package, its versi
87
87
> Pipeline Artifacts and Pipeline Caching are exempt from storage billing.
88
88
89
89
> [!CAUTION]
90
-
> Deleting a pipeline run will result in the deletion of all Artifacts associated with that run.
90
+
> Deleting a pipeline run results in the deletion of all Artifacts associated with that run.
91
91
92
92
### Use .artifactignore
93
93
@@ -104,7 +104,7 @@ Packages in Azure Artifacts are immutable. Once you publish a package, its versi
104
104
```
105
105
106
106
> [!IMPORTANT]
107
-
> Azure Artifacts automatically ignore the *.git* folder path when you don't have a *.artifactignore* file. You can bypass this by creating an empty *.artifactignore* file.
107
+
> Azure Artifacts automatically ignore the `.git` folder path when you don't have a `.artifactignore` file. You can bypass this by creating an empty *.artifactignore* file.
108
108
109
109
## Download artifacts
110
110
@@ -352,7 +352,7 @@ If you want to be able to access your artifact across different stages in your p
352
352
353
353
### Example
354
354
355
-
In the following example, we will copy and publish a script folder from our repo to the `$(Build.ArtifactStagingDirectory)`. In the second stage, we will download and run our script.
355
+
In the following example, you'll copy and publish a script folder from your repo to the `$(Build.ArtifactStagingDirectory)`. In the second stage, you'll download and run your script.
356
356
357
357
```YAML
358
358
trigger:
@@ -449,9 +449,9 @@ Once your pipeline run is complete, follow these steps to view or download your
449
449
450
450
A: Build artifacts are the files generated by your build. See [Build Artifacts](build-artifacts.md) to learn more about how to publish and consume your build artifacts.
451
451
452
-
#### Q: Can I delete pipeline artifacts when re-running failed jobs?
452
+
#### Q: Can I delete pipeline artifacts when rerunning failed jobs?
453
453
454
-
A: Pipeline artifacts are not deletable or overwritable. If you want to regenerate artifacts when you re-run a failed job, you can include the job ID in the artifact name. `$(system.JobId)` is the appropriate variable for this purpose. See [System variables](../build/variables.md#system-variables) to learn more about predefined variables.
454
+
A: Pipeline artifacts are not deletable or overwritable. If you want to regenerate artifacts when you rerun a failed job, you can include the job ID in the artifact name. `$(system.JobId)` is the appropriate variable for this purpose. See [System variables](../build/variables.md#system-variables) to learn more about predefined variables.
455
455
456
456
#### Q: How can I access Artifacts feeds behind a firewall?
0 commit comments