Active feature branch is not triggering wildcard build Follow
I'm using TeamCity 2019.2.1. The build queue is active and the build is compatible with my agent. I have committed to a feature branch (logical name: task/terraform-infra) and it shows up on the project page as an active branch with pending changes, but the build is simply not triggered. Is there something wrong with my configuration?
My VCS root is configured like so:
And I have additional VCS options like so:
I have triggers defined like so:
Please sign in to leave a comment.
Thank you for providing the screenshots. It looks like it is configured correctly from what you have shown me here. Do you have any checkout rules configured for this VCS?
Eric Borchardt that would be visible in one of the screenshotted sections, right? Anyway, I don't have anything else configured, as far as I know, around checkout rules.
No, I cannot see if you have any checkout rules applied to your VCS root from your screenshots. They are all the way over to the right hand of your screen, see below. Clicking on the Edit checkout rules button will pop-up a menu to view/change these rules.
Ahh, I see it now. I have zero checkout rules:
So it would seem you have the correct settings applied for monitoring the branch, task/terraform-infra. Let's examine your pending changes, as you did mention the changes were being detected and were showing as Pending Changes on the project page. Does your pending changes detail page contain any information regarding compatible agents or required dependencies?
I have only one agent, and it's compatible with all configs:
And looking at my project overview like you indicated, there aren't any problems shown:
I enabled debug logging and found this message in the VCS log... does this help? I'm not sure what lastTriggeredBy is referring to, or what triggering rules are not matching.
The lastTriggeredBy is the parameter that contains the id of the change that last triggered a build. That specific value really doesn't point to anything meaningful in this context, but the "There are new pending changes found, but none of them were matched by triggering rules" portion of the log entry seems to indicate the trigger excludes the pending change(s) in this case.
Could you take a screenshot of the VCS Trigger like the one I have attached?
Eric Borchardt definitely, here's that window! I do have the quiet period enabled, but the log messages from later on just state that there are no changes, so skipping triggers.
Can you please take a screenshot of the pending changes tab with the boxes checked for Show graph and Show files. If there is sensitive information, you can use the Submit a Request button at the top of the page and I'll find it there. Thanks!
Eric Borchardt no worries, nothing sensitive here.
Thanks, Michael. It seems we are dealing with something out-of-the-ordinary in your case. If you submit another change to task/service-deploy, does it trigger? Or is this stuck altogether?
Eric Borchardt I agree! But no, it doesn't matter whether I commit to the same branch, a different feature branch, or even master. Nothing gets triggered via VCS automatically (dependency builds do get triggered, just nothing from VCS triggers).
Michael, I'd like to look at some of your log files if that would be okay with you. Can you please perform the following:
I will watch for your request and then review these log files to, hopefully, get a better idea of what is going on.
No problem at all, I've submitted the request. Thanks!