Skip to content

Commit b443124

Browse files
author
Rami Bououni
committed
blocking issue
1 parent 4285ec5 commit b443124

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/pipelines/artifacts/pipeline-artifacts.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Packages in Azure Artifacts are immutable. Once you publish a package, its versi
8787
> Pipeline Artifacts and Pipeline Caching are exempt from storage billing.
8888

8989
> [!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.
9191

9292
### Use .artifactignore
9393

@@ -104,7 +104,7 @@ Packages in Azure Artifacts are immutable. Once you publish a package, its versi
104104
```
105105
106106
> [!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.
108108
109109
## Download artifacts
110110
@@ -352,7 +352,7 @@ If you want to be able to access your artifact across different stages in your p
352352

353353
### Example
354354

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.
356356

357357
```YAML
358358
trigger:
@@ -449,9 +449,9 @@ Once your pipeline run is complete, follow these steps to view or download your
449449

450450
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.
451451

452-
#### Q: Can I delete pipeline artifacts when re-running failed jobs?
452+
#### Q: Can I delete pipeline artifacts when rerunning failed jobs?
453453

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.
455455

456456
#### Q: How can I access Artifacts feeds behind a firewall?
457457

0 commit comments

Comments
 (0)