I started with this problem at the grafana community form here
As far as I'm aware, there's not a way to run a specific version of k6 with a yaml file and azure pipelines. The task in the yaml file will always download the latest binary and run it. I need to make some major adjustments to my k6 tests, or else the metric names will break them with k6 v0.48.0. I was hoping for a workaround to make sure the pipeline keeps running 0.46.0 (or a couple versions earlier), until I can get time to fix these tests. The yaml task:
- task: k6.k6-load-test.custom-build-release-task.k6-load-test@0
I started with this problem at the grafana community form here
As far as I'm aware, there's not a way to run a specific version of k6 with a yaml file and azure pipelines. The task in the yaml file will always download the latest binary and run it. I need to make some major adjustments to my k6 tests, or else the metric names will break them with k6 v0.48.0. I was hoping for a workaround to make sure the pipeline keeps running 0.46.0 (or a couple versions earlier), until I can get time to fix these tests. The yaml task:
- task: k6.k6-load-test.custom-build-release-task.k6-load-test@0