Currently on the release CI we have three x64 machines:
These three machines service two builds:
We have observed long build times, usually due to ccache invalidation/not being populated. For the latter the theory is that having three machines may be actively working against ccache since for a given build only two of the three machines would be used (so the third will not have an updated ccache cache).
I'm going to take the second IBM hosted release machine offline, leaving one Digital Ocean hosted and one IBM hosted machine. For now we'll keep both labels on both machines, but reserve the option to pin each of the remaining machines to one of the build types.
Currently on the release CI we have three x64 machines:
These three machines service two builds:
We have observed long build times, usually due to ccache invalidation/not being populated. For the latter the theory is that having three machines may be actively working against ccache since for a given build only two of the three machines would be used (so the third will not have an updated ccache cache).
I'm going to take the second IBM hosted release machine offline, leaving one Digital Ocean hosted and one IBM hosted machine. For now we'll keep both labels on both machines, but reserve the option to pin each of the remaining machines to one of the build types.