Please add Process Parameters about azure-pipelines-yaml HOT 10 CLOSED

In order to consolidate to fewer feedback channels, we've moved suggestions and issue reporting to Developer Community. Sorry for any confusion resulting from this move.

from azure-pipelines-yaml.

How about an actual link to the corresponding issue over there?

from azure-pipelines-yaml.

In order to consolidate to fewer feedback channels, we've moved suggestions and issue reporting to Developer Community. Sorry for any confusion resulting from this move.

from azure-pipelines-yaml.

In order to consolidate to fewer feedback channels, we've moved suggestions and issue reporting to Developer Community. Sorry for any confusion resulting from this move.

from azure-pipelines-yaml.

Yes, but where is this issue covered? It's like I'm talking to a send-only bot... :]

from azure-pipelines-yaml.

any update?

from azure-pipelines-yaml.

I am as well interested in this feature. The workaround proposed above is not really nice as you end up with some quite noise in the yaml.

Could it be that this PR is related to this issue: #129?

from azure-pipelines-yaml.

I have the same problem when using templates. For this particular case, I found a workaround and can use different job templates for different OS. However, this bug blocks me from implementing another required functionality, e.g., applying templates with the number of steps for a particular case depending on build options. Do you have any updates on the status of fixing this?

# File: azure-pipeline.yml

trigger:
- master

variables:
  osMacOS: macOS
  osLinux: Linux

jobs:
- template: templates/template-job.yml
  parameters:
    os: $(osMacOS)
    name: macOS_debug
    vmImage: 'macOS-10.13'

- template: templates/template-job.yml
  parameters:
    os: $(osLinux)
    name: Linux_debug
    vmImage: 'ubuntu-16.04'

# File: templates/template-job.yml

parameters:
  os: ''
  name: '' 
  vmImage: ''
  
jobs:
- job: ${{ parameters.name }}
  pool: 
    vmImage: ${{ parameters.vmImage }}
  
  steps:
  # FIXME: This "if condition" does not give "True" because parameters.os is not set to 'macOS' when it should be
  - ${{ if eq(parameters.os, 'macOS') }}:
    - script: echo Mac
# FIXME: The same problem as above
  - ${{ if eq(parameters.os, 'Linux') }}:
    - script: echo Linux

from azure-pipelines-yaml.

All of the above. I have got a huge multi-stage pipeline that relies heavily on runtime variables. I cannot set runtime variables in the yml file itself so i have resorted to having them in the UI of the pipeline definition, but this does not solve the issue as the variables are not expanded during the runtime yml creation. The parser does not expand the variables so it cannot validate the yml conditions. I'm used to that since I have been using Jinja2 templates for a long time and I've wrongly assumed this works here in a similar fashion. However it does not which has forced me to put the conditions in the low level step templates resulting in a pipeline that includes all the steps but simply skips some of them. This is very annoying to maintain.

from azure-pipelines-yaml.

I moved it into DC: https://developercommunity.visualstudio.com/idea/1008340/please-add-process-parameters.html

Use Follow button on the right to track it

from azure-pipelines-yaml.