[21:04:51] <pombreda> techalchemy: your recent forays on azure pipelines matrix generation for pip shims have proven super useful as examples :)
[21:19:27] <techalchemy> pombreda: nice, thanks, that was a pain to figure out how to do
[21:19:32] <techalchemy> there's like 30 commits probably of me attempting
[21:20:23] <pombreda> techalchemy: I am sure thet this was superbly painful... as I did also ~30 commits without something working at all
[21:20:33] <pombreda> so I am very grateful you got something :)
[21:21:25] <techalchemy> every time i try to do anything on azure it takes me many, many attempts
[21:21:36] <pombreda> techalchemy: if that's ever of use to you https://github.com/nexB/scancode-toolkit/tree/295-tests-and-setup .. and eventually adding more macos, more windows and linux distros soon enough there
[21:22:09] <pombreda> getting azure working has been a journey in rabbit holes digging indeed :D
[21:28:24] <pombreda> techalchemy: thanks to your hard work I now can generate all the tests jobs I need ... at last! https://dev.azure.com/nexB/scancode-toolkit/_build/results?buildId=277
[21:29:11] <pombreda> techalchemy: need to go. Thank you again! :)
[21:30:07] <njs> azure actually does have some wacky macro-like facility, where you can run an azure pipeline step that spits out magic escape sequences that create new azure pipeline steps just for the current build
[21:30:52] <pombreda> njs: yeah... that's a tad confusing to say the least
[21:34:04] <njs> yeah I haven't looked at it in any detail. my strategy with azure has been to put the absolute minimum in the yaml and then get into bash ASAP
[21:36:00] <techalchemy> yeah their yaml syntax is very hard to work with and their documentation is not helpful