![]() The filter applies to public repositories only. It must have either the public_repo (for public repisotories) or repo (for private repositories) scope. Use a personal access token or obtain a token through an OAuth connection. This option will not work if the VCS root employs anonymous authentication or SSH.įor a GitHub Enterprise repository, only the personal access token/ x-oauth-basic pair will work. TeamCity will try to extract username/password credentials or a personal access token/ x-oauth-basic from the VCS root settings if the VCS root uses HTTP(S) fetch URL. See the example on how to set up TeamCity to run builds on pull requests. To achieve this, enable and configure the Pull Requests and Automatic Merge build features. The build feature parameters depend on the selected VCS hosting type.įor requests from GitHub and GitLab, you can set up TeamCity to automatically run a build on each request and merge the request if the build is successful. When adding this build feature, you need to specify a VCS root and select a VCS hosting type. The branch specification of the VCS root must not contain patterns matching pull request branches. It monitors and triggers builds only on head branches (such as refs/pull/*/head).Īfter a build is run on a pull request, TeamCity provides additional details for the pull request branch on the Build Overview page. The feature extends the original branch specification of the VCS roots, attached to the current build configuration, to include pull requests that match the specified filtering criteria. The Pull Requests build feature lets you automatically load pull request (or merge requests in case of GitLab) information and run builds on pull request branches of the following VCS (Version Control Systems) hosting services:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |