Quantcast
Channel: TeamCity : Powerful CI/CD for DevOps-centric teams | The JetBrains Blog
Viewing all articles
Browse latest Browse all 916

Comment on Building GitHub pull requests with TeamCity by Stefan F

$
0
0

Is it possible to support multiple repositories with the pull request feature?

We have builds using three git repos and the ‘feature branch’ thing which selects same branch name with
fallback to default between the repos works fine.

What I want to do with the pull requests are to verify them by building ‘refs/pull-requests/###/merge’
(### is some number)
Earlier comment mention that setting teamcity.pullRequests.buildBranchFilterEnabled should enable build/verification of the merge branch.

The issue/challenge is to get the build to use related pull requests between vcs repos.
Example,
repo A: Pull request 37 feature/ABC-321 -> dev ( refs/pull-requests/37/merge )
repo B: no branch nor pull req, should use default ‘dev’ ( dev )
repo C: Pull request 85 feature/ABC-321 -> dev ( refs/pull-requests/85/merge )

I’d like the pull request verification build to use the branches inside parenthesis above.

(yes, there can be a race issue depending on which order the PRs are created but the second
build should be ok using the related pull requests)

In short, can we ‘connect’ pull requests between repos in a similar way as the feature branch by name mechanism.
Need to look at source and destination branch of the pr.


Viewing all articles
Browse latest Browse all 916

Trending Articles