How to limit only one build per branch per build configuration?
I have build configuration. It has VCS triggers on two branches dev (default) & release.
If i dont limit number of simulatenous build to 1, it triggers many builds on any branch. So i decided to Limit it to 1, will this run 1 build at a time per branch per build configuration
Please sign in to leave a comment.
Hi,
this will run only one build at a time per build configuration, but it won't stop them from being triggered, they will just be triggered at the same time but will wait in the queue to be run sequentially.. Why are many builds on any branch getting created? Is it what you would expect with your configuration?
Hi,
Has anything changed since 2017? We are running E2E integration tests in TeamCity. The tests need a Kubernetes cluster. It takes 10+ minutes to provision a new cluster in Azure so it is not feasible to provide each build with each own cluster. Our current solution is to provision one cluster per branch. That seems to work as long as we don't have multiple builds for the same branch running at the same time. Any recommendations
Thanks
A lot has changed in regards to Kubernetes support since 2017. Now we have a dedicated kubernetes plugin and added a large amount of docker features, so you might want to take a look at those first.
In regards to limiting builds per branch nothing has changed from TeamCity's point of view. You might be interested in checking this feature request, which includes among other things a third party plugin with the feature: https://youtrack.jetbrains.com/issue/TW-22960
Hi,
One of the responsibilities of the app we are building is to provision K8s clusters so we can't really use what TC has to offer.
Re the plugin, it looks like will affect the whole server whereas I need this behaviour in one build config only. I will link to this thread. Hopefully, this will add some weight.
Hi Pawel,
Feel free to watch, vote or comment on the issue. The plugin adds the option to the server, but seems to be enabled on a per-project/per-build config basis via a property, at least according to their readme. If I'm misunderstanding it, it should still be possible to pull it and adapt it to your needs.