Hi!
I'm working with this amazing task for a long time. Now, we are migrating to Azure Devops YAML Pipelines and improving the mecanism.
I made a pipeline that is triggered manually and download the artifacts from other build pipeline.
I think due to the nature of pipelines this task is not able to recognize the build pipeline from which the artifact is downloaded. That's why I get the following text:
Debugging, I found that is taking the BuildId from the pipeline that is Running and not the BuildId from the build pipeline.
Looking at the code I found that it is getting the BuildId of the environment, and this variable is not overridable.
'''
settings.buildId = parseInt(tl.getVariable('Build.BuildId'));
'''
Could you add the possibility to parameterize the BuilId (with another name, obviously) so that taks could go to grab the work items related to that particular build?
I believe that is not a complex situation to fix
Thanks in advance!
Hi!
I'm working with this amazing task for a long time. Now, we are migrating to Azure Devops YAML Pipelines and improving the mecanism.
I made a pipeline that is triggered manually and download the artifacts from other build pipeline.
I think due to the nature of pipelines this task is not able to recognize the build pipeline from which the artifact is downloaded. That's why I get the following text:
Debugging, I found that is taking the BuildId from the pipeline that is Running and not the BuildId from the build pipeline.
Looking at the code I found that it is getting the BuildId of the environment, and this variable is not overridable.
'''
settings.buildId = parseInt(tl.getVariable('Build.BuildId'));
'''
Could you add the possibility to parameterize the BuilId (with another name, obviously) so that taks could go to grab the work items related to that particular build?
I believe that is not a complex situation to fix
Thanks in advance!