Eldarrin

I'll run some tests here and see if I can duplicate it

If you run curl -u user:pat https://dev.azure.com/FOO/_apis/distributedtask/pools/90/jobrequests it should spin up an agent for each item in that list that has value.n.results = nil its performing correctly here in my...

added a sample of my thinking

Well the only way to maintain backwards is to add a new variable to the scalerconfig or we need to rewrite every scaler to match. Don't see another way.

@zroubalik I can design something that will work with 2.x if you are interested, but happy to leave it to 3.x

IT looks fine to me, there is an existing function that already strips the agent version from the demand array so that could be extended. Although I would suggest looking...

If you are struggling reach out and I can help. If the documentation is insufficient I probably need to improve it :)

Needs some work, but I need a git scaler to sit alongside my azure pipelines scaler so writing one. It currently has the issue of if you have a lot...

@tomkerkhove this is working in my dev clusters now. I haven't done a webhook version, this is a scale to zero, pull awaiting jobs version. Would you like this submitting?...

Yeah, all using the rest api. Will document it and submit a PR. Cheers, Andy