So there is data to support these builds used to take a *lot* less time.
Exploring alternative compilation methods such as distcc is completely out of scope at this time. Ccache might be a little more attainable as we've used it in the past. There may be something off in the trusty pbuilders, it's possible the slowness started with that transistion. That's something I can try to investigate.
The most recent version of the mir-android build took 11 minutes: /jenkins. qa.ubuntu. com/job/ mir-android- trusty- i386-build/ 914/
https:/
But this lead me to look for the 'saucy' version for the other jobs and I found a comparison:
https:/ /jenkins. qa.ubuntu. com/job/ mir-saucy- armhf-ci/ 103/ == 30 minutes /jenkins. qa.ubuntu. com/job/ mir-trusty- armhf-ci/ 35/ == 94 minutes
https:/
So there is data to support these builds used to take a *lot* less time.
Exploring alternative compilation methods such as distcc is completely out of scope at this time. Ccache might be a little more attainable as we've used it in the past. There may be something off in the trusty pbuilders, it's possible the slowness started with that transistion. That's something I can try to investigate.