Using an dynamic expression from a variable coming from a script execution

Question

I have a working yaml build pipeline where I maintain the major, minor and patch versions of my app. The revision is calculated by the pipeline with this expression:

revision: $[counter(variables['squilversionkey'], 0)]

(The key is calculated from the other variables to give something like "1.1.20-dev".)

In the same pipeline, I pass this to a script that sets the revision and combined versions (such as "1.1.20.11-dev") in some text files so that the app knows its version. So far, that works.

Ideally though, I don't want to maintain the major, minor and patch versions in the same yaml file. It's a complicated file and I don't want to see it as changed in the commit history just because the versions are bumped when the logic isn't changed.

In order to have those in a different file, I need to read those values into the pipeline though (they are no longer in the yaml). That works in principle:

Write-Output "##vso[task.setvariable variable=squilversionkey]$baseVersion"

This should give me the variable to use in the counter expression, right?

Alas, the counter expression needs to be "dynamic" (in square brackets), and those can only appear in variable definitions and conditions - not in the env sections of tasks.

Tasks can also not have variable definitions of their own, only jobs. But a new job will have forgotten the variable and it also seems a bit overkill to bother a second job.

What's a good way to do this?

I introduced two methods of setting persistent variables for pipeline runs. Neither of these will produce a commit history. You can generate the version in any way you want and store it. You can then use these variables anywhere in the pipeline where the runtime is supported. See my answer. :) — Bowman Zhu
– Bowman Zhu, Commented Nov 22, 2022 at 7:14

Bowman Zhu · Accepted Answer · 2022-11-22 07:10:58Z

1

I don't want to see it as changed in the commit history just because the versions are bumped when the logic isn't changed.

Since you have this requirement, then obviously you shouldn't make any changes in the repository.

The following introduces two methods of setting persistent variables for pipeline run (neither will generate commit history). You can choose one of them.

1, A suggestion is store the data in other places, for example, variable group:

Variablegroups - Update

And then get it from the variable group:

Variablegroups - Get

Also you can simply using YAML to get the variable like this:

trigger:
- none

pool:
  vmImage: ubuntu-latest
variables:
- name: squilversionkey
  value: 1
- name: revision
  value: $[counter(variables['squilversionkey'], 0)]
- group: MyGroup


steps:
- bash: |
   echo $(revision)
   echo $(versionxxx)
- bash: |
   echo $abc
  env:         #get the env of the task from variable group. Directly using the variable name in variable group is ok.
   abc: $(versionxxx)

This is my variable group:

I can successfully get the value from it via the above YAML(using env section of the task can easily process the value during runtime):

2, Another suggestion is to update the variable of your pipeline(Not from YAML), and then use the variable from the pipeline.

I mean the variable in this place:

The variable in this place will not affect the content of the repository, so it will also not generate unrelated commit history in repository.

For example, you made a active variable:

Using this REST API to get the variable of the pipeline definition:

Build Pipeline Definitions - Get

Result on my side:

And use this REST API to update the variables of the pipeline.

Build Pipeline Definitions - Update

answered Nov 22, 2022 at 7:10

Bowman Zhu

7,5941 gold badge13 silver badges16 bronze badges

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

1 Comment

John Over a year ago

I do think it should be in the sources because I might have different branches with different versions (a stable 1.1 getting only fixes and a yet unstable 1.2, for example). I just don't want it in the same yaml where the all the build logic lives because then I couldn't see from the logs when the build logic changed any longer. But that is one elaborate answer nonetheless. I feel a bit bad for it not really solving my issue...

Collectives™ on Stack Overflow

Using an dynamic expression from a variable coming from a script execution

1 Answer 1

1, A suggestion is store the data in other places, for example, variable group:

2, Another suggestion is to update the variable of your pipeline(Not from YAML), and then use the variable from the pipeline.

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1, A suggestion is store the data in other places, for example, variable group:

2, Another suggestion is to update the variable of your pipeline(Not from YAML), and then use the variable from the pipeline.

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related