No, it hasn't been a problem for me. To be honest, I've moved on to employment that doesn't need Qt. However, I contributed the basis of the matrix build generator for aqtinstall using Azure Pipelines and in chatting with some of the comma.ai openpilot developers, they were interested in a similar system for one of their projects. I cited my contribution as an example. Another interested user ported the approach to GitHub Actions with my implementation as an example. comma.ai's staff deemed it to be not worth the maintenance to accept and passed.
I would like @lsrugo's effort to not go to waste. Perhaps it might be worth a port? In https://github.com/miurahr/aqtinstall/issues/651, there was some concern about build minutes used. Additionally, keeping the builds in the GitHub ecosystem helps reduce another service having to be used or setup.
There's also the concern about the health of Azure Pipelines. They do use it internally at Microsoft, but they are clearly positioning GitHub and GitHub Actions to be the successor or current recommendation for the general public.
The solution
Look at https://github.com/commaai/bodyjim/pull/11 , and use its approach to port things back. For speed, it might be nice to also gate the matrix on higher "tier" jobs to be run.
Alternatives you've considered
No response
Additional context
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Is your feature request related to a problem?
No, it hasn't been a problem for me. To be honest, I've moved on to employment that doesn't need Qt. However, I contributed the basis of the matrix build generator for aqtinstall using Azure Pipelines and in chatting with some of the comma.ai openpilot developers, they were interested in a similar system for one of their projects. I cited my contribution as an example. Another interested user ported the approach to GitHub Actions with my implementation as an example. comma.ai's staff deemed it to be not worth the maintenance to accept and passed.
I would like @lsrugo's effort to not go to waste. Perhaps it might be worth a port? In https://github.com/miurahr/aqtinstall/issues/651, there was some concern about build minutes used. Additionally, keeping the builds in the GitHub ecosystem helps reduce another service having to be used or setup.
There's also the concern about the health of Azure Pipelines. They do use it internally at Microsoft, but they are clearly positioning GitHub and GitHub Actions to be the successor or current recommendation for the general public.
The solution
Look at https://github.com/commaai/bodyjim/pull/11 , and use its approach to port things back. For speed, it might be nice to also gate the matrix on higher "tier" jobs to be run.
Alternatives you've considered
No response
Additional context
No response
Code of Conduct