How do TeamCity evaluate Active or Inactive Stash Pull Request Branches?
I have configured TeamCity to build Pull Requests. The branch specification is like
+:refs/pull-requests/*/from
-:<default>
-:master
This works fine but there are some requests which have been declined/merged still the teamcity build show them (highlighted). Also there is a pull request No. 228 which is shown in Inactive Branches.
So, how are Inactive and Active branches evaluated and how can I make these 2 go away and bring the requested PR as active one.
Please sign in to leave a comment.
Hi,
Inactive branches are described here: https://confluence.jetbrains.com/display/TCD10/Working+with+Feature+Branches#WorkingwithFeatureBranches-Activebranches
Basically they are branches that haven't had a commit/build in some time. Adding a new commit or forcing a new build should bring the branch out of inactivity.
In regards of picking up requests that have been declined or merged, this is going to depend on the exact process. TeamCity by default pulls data from github every 60 seconds, unless you have modified this value. If in one of those requests, the new branch was detected but it hadn't been marked as closed by the remote server, then its contents would have been pulled and builds likely triggered.
If this isn't the case, we would need more information on what exactly happened in order to investigate.