Provide build configuration dependencies in TFS Build
Provide the ability to create build configuration dependencies such that the success of one build configuration can trigger another build configuration such as a successful build triggering the building of an installation package or a build configuration which deploys to a development or staging server. Other tools such as Cruise Control.Net and Jetbrains TeamCity already offer build configuration dependencies/build configuration triggering through various means, therefore, TFS Build should also provide this type of support.
I wonder how people are configuring Continuous Delivery Pipelines for Microservices-Architectures without this feature.
Please don't add fancy features in the VSTS-UI but focus on accomplishing real world-scenarios!
Please learn from GoCD: https://www.gocd.io/assets/images/videos/go-value-stream-map-d215777c.jpg
Guys! We NEED it!
This is a fundamental requirement of any build system.
TeamCity has had this forever.
Richard Hundhausen commented
I've not used it, but I see a Trigger Build Task in the Marketplace that enables the chaining of builds within TFS/VSTS.
Ronald Wassenaar commented
This would be a very nice feature. Other build systems already support this feature; so why not TFS?
this is an important feature, it is in all build systems i have worked with.
Also TFS 2015 has a problem that it does not allow build from multiple branches .this should also be addressed ASAP
Robin Paardekam commented
I totally support this idea. In the meantime I will continue to implement this on my own projects through the API (https://www.visualstudio.com/en-us/docs/integrate/api/build/builds). It is not that difficult to queu another build by adding a PowerShell-task at the end of an existing definition. An objection against it is that maintaining it is quite time consuming.
Harald K commented
I would very much appreciate such a feature on TFS as well. Other CI servers offer this: Jenkins for example. This would be critical for our company!
The idea was posted in 2011. This feature seems to be pretty simple. Why wasn't it implemented yet?
Lou machado commented
This feature is critical. Without it there is no way to equivalently match activities you can do in Windows Workflow. For larger, complex builds we need a way to manage things so we aren't stuck going iteratively through steps (which wastes processor cycles).
Very important feature. I don't know how to handle complex build process like in real organization without this feature. Please add this to TFS 2017.
Alexey Murashkevich commented
Please add this feature!!!
My Vote to this. I am working as DevOps SME and at the same time need to do tools rationalization/consolidation, we can not proliferate multiple ecology for every bit of DevOps. We need to get rid off Cruse Control and others. This feature will help us to bring everybody into a Single-Integrated platform - TFS.
As this seems to be planned, I wish it will seep into latest release !!
I also like to add a vote for this. I'm a DevOps engineer as well, and i'm forced to leave the TFS ecosystem because of the lack of this feature. Please do something ASAP!
I vote for it too as this will be a great feature as it will really leverage the power of TFS further.
This is a crucial feature for the usability of the build engine. It should also be possible to use the artifacts from one build definition in the another build definition.
Please add this feature! This is a major roadblock for our team.
Faris Shomou commented
As a DevOps architect and teamcity administrator, build configuration dependencies is a very powerful feature in teamcity. I do recommend to implement this feature in TFS.
Could you please give us an update when this feature will really "planned"? This would be great. We can't wait to somehow set up a kind of build chain for the TFS. Thanks!
When can we change "PLANNED" to "STARTED"? It is about time... I still and really cannot believe that this feature is still not implemented. Not even the slightest support. Just unbelievable! Sorry, but this is frustrating...