azure devops, classic pipelines: Using parameters in custom conditions

Question

Summary: How to skip a task in a Azure Devops Task Group based on a parameter value, using Classic Pipelines.

Hi,

In Azure DevOps using Classic Pipelines, I have a Task Group with parameters and I want to use one of these parameters to decide if one of the tasks should be executed. I tried every format I could find but I am never able to get the parameter value when running this group.

parameter: condition:

task group configuration:

I've tried the following notations and probably some more, but nothing worked. Either there was an error in the building process or the variable was evaluated to NULL.

not(eq(variables['parameters.CustomKey'], '-'))

not(eq(variables['CustomKey'], '-'))

not(eq('${{ variables.CustomKey }}', '-'))

not(eq('${{ parameters.CustomKey }}', '-'))

I followed what is explained here but it seems most explanations are for YAML and not classic pipelines.

Any help would be appreciated. Thanks!

Shamrai Aleksander · Accepted Answer · 2021-02-25 12:22:04Z

4

Here is an example from my task group:

In your case, the second option is close to being true. Try to use the custom condition:

and(succeeded(), ne(variables['CustomKey'], '-'))

answered Feb 25, 2021 at 12:22

Shamrai Aleksander

16.6k4 gold badges27 silver badges38 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

donelodes Over a year ago

You're absolutely right, used your condition and it worked! I don't know what I was doing wrong, maybe it was the ne instead on not(eq( or maybe the and + succeeded... either way thank you!

Collectives™ on Stack Overflow

azure devops, classic pipelines: Using parameters in custom conditions

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related