[build] Moved image-builds between cloud and hosted servers #1839
Conversation
- 30min and less are built in the cloud - the rest are built on hosted servers, even if that means they are even slower Signed-off-by: Roland Asmann <roland.asmann@gmail.com>
| @@ -93,6 +92,7 @@ jobs: | |||
|
|
|||
| - lang: dotnet10 | |||
| distro: debian | |||
| runner: macos-hosted | |||
There was a problem hiding this comment.
Already tried moving dotnet10 to macos-hosted once and it was crashing for some reason. Will be nice to see how it performs now.
There was a problem hiding this comment.
During my testing, I had. varied results, but the error (an issue with downloading a docker image from Microsoft) occurred both in the cloud and hosted, so... But we'll see, we can always change it back if it doesn't work out too well.
|
We do have another Mac mini, but it is being used up by vdb. There is an issue with Docker in that only one token can be active at a time. So if there are two actions runners, only one of them can perform Docker builds. There are some workarounds suggested to create separate contexts, etc., but it all sounded too complex. We have the mini-dev-1, which is used up by the almalinux builds. |
|
I had included some of our other servers in another branch I was working on, but some of them seem to have issues as well. I might come back to that at some other point and try to figure out why they are acting so strange and then add them when things are hopefully fixed. |
So far, several images build faster on hosted, some are the same.
Because we currently only use a single hosted server, there's a bit of a queue there though, but at least we don't use up all cloud compute so fast...