Open vriesmarcel opened 7 years ago
Hi @vriesmarcel and thank you for your feedback! 😃
That was something we were thinking about when we designed this extension, as we wanted to release a set of tasks to get more control on the builds and releases flows. But we weren't alone, and the good news is that your scenario is something Microsoft is planning to release OOTB during 2017 Q1 :
https://blogs.msdn.microsoft.com/bharry/2017/03/06/team-servicestfs-roadmap-update/
Build improvements – Multi-phase builds, conditional tasks, shared variables: There are some pretty important improvements here that enable you to scale out your builds across multiple agents and have “merge points” – this is one of the things “phases” gives you. Conditional tasks also allows you to reduce the number of very similar build definitions you have and use conditionals instead.
Do you think you would use these new conditional tasks? Or do you think it won't be adequate for your scenario? Let us know! 😃
@vriesmarcel did you have time to consider what Adrien wrote?
It would be great if you could add the capability not to queue the build if a certain condition is met. either just an environment variable that is true or false or an expression of variables that match the Boolean true or false. this way I can use one build to trigger other builds based on some logic we have that determines if a rebuild is required