Azure-pipelines-tasks: Support for running tasks conditionally

[jmezach]

I was wondering if any support is planned for running tasks in a build conditionally. For instance, run a particular task only for the release configuration, or run a task only for a particular branch. Currently I'm putting this logic into the tasks themselves, but it would be great if this was supported by the task runner somehow making it a bit more flexible.

[bryanmacfarlane]

We do have it on our backlog to condition tasks on trigger type (CI, scheduled).

[pascalberger]

:+1:

@bryanmacfarlane Do you plan to only condition on type of trigger (ci, scheduled) or also on trigger details like branch who triggered the build (would be really useful).
Or more general to run tasks conditionally on any condition with support for variable expanding. This would allow to set in a first step some variables and use them later as condition.

[bryanmacfarlane]

That's why I mentioned it - feedback welcome but we want to keep it reasonable :) Variables was the other one but it might be limited to exists or equals

[jmezach]

If we could specify something like $(BuildConfiguration) equals "Release" on a task that would be extremely helpful.

[bryanmacfarlane]

OK - adding to our backlog for our service. (not a task issue)

[dnelly]

Any updates on this? This would be extremely helpful right now. I could cut down on what get's copied for uploading which would save me about a gig of data transfer.

[brphelps]

@bryanmacfarlane -- Is there another issue created that replaced this?

[bryanmacfarlane]

This was implemented in agent and service so tracked there

That said it's in production now in preview. You have to opt into new designer (user) and then enable conditional tasks ( account level ). Opt in from context menu on profile

[bryanmacfarlane]

https://www.visualstudio.com/en-us/docs/build/concepts/process/conditions