Allow Package variable type for step template
I would like to create a step template to run some Postman test suite. For this I thought to pass the test files and environment files to the package. Extract the package somewhere, run powershell in the extracted package and call newman (command line runner for postman).
But I can't add a 'Package variable' to a step template (like for a deployment step.
It would be nice to have this as variable for a step template. In the process, you would then get a dropdown with the available packages, and a dropdown with the possible packagefeeds. The script would then automatically extract the package on the selected deployment target(s), and run powershell inside the context of that package.
This way I could specify relative paths to the files needed as input for the script.
My bad entirely, in fact: My channel rules was not applied to the new steps created. Sorry!
Sorry. My comment is confusing. It seems that it is possible to select a package version for a step named by a variable. However the selection rule does not consider the release channel version rules. I have a project where I want prerelease packages to be published to certain environment and release packages to be released to a another. I do not annotate the with SemVer but by legacy with version numbers in the range [1.0.0. for production and [0.7.0.0,188.8.131.52[ for development. These rules are neither enforced nor aided by the step template using a parameter variable for package names although it builds on the "Deploy a package" template.
I have tried this and does not think the result is as desired. It seems that the created step does not adhere to the channel package version rule; the package selected is simply ignoring the package number selected. I cannot find a way to select specific package versions for a deployment, which does not seem satisfactory. Hope there is a blunder on my part, though.
David Roberts commented
I believe this is already available, when creating a step template select the 'Deploy a Package' type. Much like 'Deploy a package' in a project's process. You can then customize the pre,deploy,post powershell scripts in that template.
You can't do exactly what you are stating (add a package variable) to a 'run as script' template, start from the 'Deploy a package' one and that may help.