Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit f5d4dca

Browse files
committed
format doc
1 parent 1f03c1b commit f5d4dca

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/posts/2022/2022-02-19-azure-pipeline-checkout-repository-from-another-project.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,13 @@ My first try was going the security tab of the remote repository (projectB's Pro
4545
### Create read access to the target repository
4646

4747
This method is shown [here](https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/azure-repos-git?view=azure-devops&tabs=yaml#failing-checkout) in the last use case, which is:
48+
4849
- If the scope is project? => Yes
4950
- Is the repo in the same project as the pipeline? => No
5051
- Is your pipeline in a public project? => No
5152

5253
You need to take additional steps to grant access. Let us say that your pipeline exists in project A and that your repository exists in project B.
54+
5355
1. Go to the project settings of the project in which the repository exists (B). Select Repos -> Repositories -> specific repository.
5456
2. Add your-project-name Build Service (your-collection-name) to the list of users, where your-project-name is the name of the project in which your pipeline exists (A).
5557
3. Give Read access to the account.

0 commit comments

Comments
 (0)