Teamcity doesnt trigger build on non-default branches for pending changes
|
|
I have three branches:
Have added VCS and schedule trigger for two different Build configuration. However when changes are committed to one of three, by default build triggers only for dev. VCS Trigger screenshot:
Schedule Triggers:
Builds are not triggering on release branch. Shows pending changes but doesn't trigger. We dont directly commit to release but via Pull Request.
|
Please sign in to leave a comment.
Hi Cycoraxdev,
I think the schedule trigger issue is that the format for minutes should be "0/2" instead of "*/2" if you want to run it every two minutes (see more details here: https://confluence.jetbrains.com/display/TCD10/Configuring+Schedule+Triggers )
The VCS Trigger is weird that doesn't trigger, but if the schedule trigger has been blocking the triggering it might be because of that. It's not unlikely that you will need to restart the server after the change if this is the case. Could you check?
I set 0/2, but still on non-default branch it shows pending changes, but instead it trigger on default branches which doesn't have changes, This is not good behaviour. On this build configuration we have only one trigger.
NOTE: we dont directly checkin to release but via Pull Request from feature branch
I had read about your checkins, but as long as the branch is detected to have changes, and it has the VCS Trigger configured it should be triggered.
As the next step, I'd like to ask you to send us the teamcity-server.log, teamcity-vcs.log and to take a couple thread dumps from the server and send them to us. Use the submit a request button above to send us the files. To get the server thread dumps please follow the steps here: https://confluence.jetbrains.com/display/TCD10/Reporting+Issues#ReportingIssues-ServerThreadDump
no VCS Trigger, i use schedule trigger. I found issue, in build configuration i added parameter teamcity.build.branch with default value as dev, though it had release as well for select option. After i delete that parameter it now triggers. I guess that was issue
but i am not sure even if pending changes VCS doesnt trigger on non-default sometimes. Teamcity is still unstable i guess
If you have set up a parameter that makes the build branch be one in particular, triggers will always take that parameter and thus build on that branch, only builds that you run manually configuring a different parameter will be run in different branches. If you don't configure such a parameter, it should work just fine. The parameter was, as you mentioned, configured in the build configuration. That impacts all triggers on it.