1
0
Форкнуть 0

Merge pull request #830 from kant/patch-4

Minor formatting proposal on paragraph #12
This commit is contained in:
jeschu1 2019-03-11 06:46:43 -07:00 коммит произвёл GitHub
Родитель 0d9a0dd5f0 8c88681117
Коммит 9270c89a0c
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 1 добавлений и 1 удалений

Просмотреть файл

@ -9,7 +9,7 @@ _Note:_ SSH is often a better choice for automated system because requiring inte
The majority of build definitions will work with a single repository, or at least a set of repositories which all have the same authentication requirements. The majority of build definitions will work with a single repository, or at least a set of repositories which all have the same authentication requirements.
In this case, it is generally better to rely on [Azure DevOps Build Variables](https://docs.microsoft.com/en-us/vsts/build-release/concepts/definitions/build/variables?tabs=batch); specifically the `$(System.AccessToken)` build process OAuth token. In this case, it is generally better to rely on [Azure DevOps Build Variables](https://docs.microsoft.com/en-us/vsts/build-release/concepts/definitions/build/variables?tabs=batch); specifically the `$(System.AccessToken)` build process OAuth token.
To enable scripts to use the build process OAuth token, go to the Options tab of the build definition and select 'Allow Scripts to Access OAuth Token'. To enable scripts to use the build process OAuth token, go to the `Options` tab of the build definition and select `Allow Scripts to Access OAuth Token`.
For more information, read [Azure DevOps: Use the OAuth token to access the REST API](https://docs.microsoft.com/en-us/vsts/build-release/actions/scripts/powershell#oauth). For more information, read [Azure DevOps: Use the OAuth token to access the REST API](https://docs.microsoft.com/en-us/vsts/build-release/actions/scripts/powershell#oauth).
## Recommendations for Other Build Services ## Recommendations for Other Build Services