first version

Author: silviuandrica

docs/pipelines/includes/information-run-include.md

@@ -0,0 +1,8 @@
+A pipeline information run tells you Azure DevOps tried running a YAML pipeline, but failed to retrieve its source code. Such a run looks like in the following screenshot. 
+
+![Pipeline information run](../process/media/pipeline-information-run.png)
+
+You can recognize a pipeline information run by the following attributes:
+- Status is `canceled`
+- Duration is `< 1s`
+- Run name contains `Could not retrieve file content for {file_path} from repository {repo_name} hosted on {host} using commit {commit_sha}`

docs/pipelines/process/information-run.md

@@ -0,0 +1,31 @@
+---
+title: Pipeline information runs
+description: What are pipeline information runs
+ms.topic: reference
+ms.assetid: 96a52d0d-5e01-4b30-818d-1893387522cd
+ms.author: sandrica
+author: silviu.andrica
+ms.date: 02/03/2022
+monikerRange: '>= azure-devops-services'
+---
+
+# Pipeline information runs
+
+[!INCLUDE [header](../includes/information-run-include.md)]
+
+## When is a pipeline information run created?
+
+The first step of running a YAML pipeline is to retrieve its source code. When this step fails, the system creates an information run. These runs are created only if the pipeline's code is in a GitHub or BitBucket repository.
+
+A pipeline may run in response to:
+- Pushes to branches in its `trigger` branch list
+- Creating or updating Pull Requests that target branches in its `pr` branch list
+- Scheduled runs
+- Webhooks called
+- Resource repository updates
+- Resource external builds complete
+- Resource pipelines complete
+- New resource package versions are available
+- Resource containers changes
+
+Here's an example of when a pipeline information run is created. Suppose you have a repo in your local BitBucket Server and a pipeline that builds the code in that repo. Assume you scheduled your pipeline to run every day, at 03:00. Now, imagine it's 03:00 and your BitBucket Server is experiencing an outage. Azure DevOps reaches out to your local BitBucket Server to fetch the pipeline's YAML code, but it can't, because of the outage. At this moment, the system creates a pipeline information run, similar to the one shown in the previous screenshot.

docs/pipelines/process/media/pipeline-information-run.png

@@ -211,6 +211,11 @@ For included branches, a build will be triggered on each push to a pull request
 
 ---
 
+## Pipeline information runs
+[!INCLUDE [header](../includes/information-run-include.md)]
+
+Learn more about [pipeline information runs](../process/information-run.md).
+
 ## FAQ
 
 Problems related to Bitbucket integration fall into the following categories:

docs/pipelines/repos/bitbucket.md

@@ -512,6 +512,12 @@ The following commands can be issued to Azure Pipelines in comments:
 
 If you have the necessary repository permissions, but pipelines aren't getting triggered by your comments, make sure that your membership is **public** in the repository's organization, or directly add yourself as a repository collaborator. Azure Pipelines cannot see private organization members unless they are direct collaborators or belong to a team that is a direct collaborator. You can change your GitHub organization membership from private to public here (replace `Your-Organization` with your organization name): `https://github.com/orgs/Your-Organization/people`.
 
+## Pipeline information runs
+[!INCLUDE [pipeline-information-run](../includes/information-run-include.md)]
+
+Learn more about [pipeline information runs](../process/information-run.md).
+
+
 [!INCLUDE [ci-triggers](includes/source-options.md)]
 
 ## Pre-defined variables

docs/pipelines/repos/github.md

@@ -69,6 +69,11 @@ To allow traffic from Azure DevOps to reach your Bitbucket Server, add the IP ad
 
 Allow Azure Pipelines to attempt accessing the Git server in the **Other Git** service connection.
 
+## Pipeline information runs
+[!INCLUDE [header](../includes/information-run-include.md)]
+
+Learn more about [pipeline information runs](../process/information-run.md).
+
 ## FAQ
 
 Problems related to Bitbucket Server integration fall into the following categories:

docs/pipelines/repos/on-premises-bitbucket.md

@@ -158,6 +158,9 @@
         - name: Job access tokens
           href: process/access-tokens.md
           displayName: job access token, identity, build service account, project build service account, collection build service account, access token, build service
+        - name: Information runs
+          href: process/information-run.md
+          displayName: information run  
     - name: Pipeline reports
       items:
         - name: View pipeline reports