Schedule trigger is triggered even when there are no changes
I have a build configuration that is triggered on a schedule (nightly).
It is marked to only execute when there are pending changes.
The VCS root that is attached to this build configuration is set to monitor a bunch of different git branches:
Notice that the default branch is 'integration', which has no changes, but other branches do have changes. I would expect the build to trigger using the branch with the pending changes, and not using the default branch, which has nothing new on it.
Please sign in to leave a comment.
Could you share a screenshot of the schedule trigger, please?
sure, here it is:
Hi Lior, sorry I wasn't specific, but the Additional options would have been what I was mostly looking for. In there you can find the branch filter, which by default will only enable builds on the default branch. More information on the branch filter here: https://confluence.jetbrains.com/display/TCD10/Configuring+Schedule+Triggers#ConfiguringScheduleTriggers-BranchFilterbranchFilter
If the branch filter is configured to enable builds for the branches you have changes in, yet all builds are triggered in the default branch, please fill an issue in our tracker: https://youtrack.jetbrains.com/issues/TW, adding please the screenshots (this time include the additional options).
Also keep in mind that in the branch filter of the trigger you have to add the "logical branch name", which in your case would be only v3.3 or whatever is after the - on the feature branches.
Our VCS root is tracking multiple branches. Other build configurations are using a VCS trigger and they trigger a build on the relevant branch when there are pending changes. I did not specifically set the branch filter on the VCS trigger to do that. Why does the schedule trigger behave any differently than this behaviour ?
As you can see here, the default behavior for VCS Triggers is also running only the default branch. https://confluence.jetbrains.com/display/TCD10/Configuring+VCS+Triggers#ConfiguringVCSTriggers-BranchFilterbranchFilter
Are you sure you haven't set anything in the branch filter for the others?
No, i just double checked. the VCS trigger will automatically trigger builds on the proper branches, but the schedule trigger will not, hence my question here, since this seemed like counter-intuitive behaviour.
If build configuration has branches, then new schedule trigger has +:* branch filter by default. Did you change the default?
i didn't change the default. there wasn't any setting like +:* there.
What could've happened (who knows since it was a while ago) was that i've created the VCS root + trigger but only then added more branches to the VCS root. not sure if this is how i did it though.
Yes, this might be the case. Schedule trigger runs only in the default branch if there is no branch specification in any VCS root of a build configuration. The rationale for that is that if we run builds in all branches, then expanding branch spec will trigger a lot of builds.