Hey,
we just released new version of Test Adapter.
Best regards,
Pawel
dfajardo :
My pipeline is not using YAML yet and therefore not sure how i can force a version to be used.
Here are the version im using:
VSTest (Visual Studio Test😞
So for VSTest I seem to be using an older version than the one you are mentioning.
But again, I don't know how to enforce a version without having to convert my pipeline to YAML which is not really what i desire at this stage.
Anyways since im using TFVC im not even able to use a YAML pipeline.
Your classic pipeline created a file called azure-pipeline.yml in the repository you setup the pipeline with. You can go to that file and directly change the version number as I pointed out. WARNING: not sure if that might mess up your ability to use the classic editor. But everything you do gets created as a azure-pipeline.yml file for classic pipelines.
dfajardo I looked at the repository and this is not the case. No yml files are there. I believe this was the case a long time ago but it is no longer the case.
I could try to manually update the pipeline using the REST api (we do this internally to update using script or pipeline whenever we need to propagate changes to our many pipelines).
I'll let you know if that works. However clearly this is not a viable solution in long term, but if it works shortterm then great.
That is worth the try on that. Otherwise, if you can't get that to work, click to yaml view (Don't save that, but save the yaml to another file) then with that yaml you could create a temporary pipeline to run and change that yaml to the correct task version.
