qmake on macos extremely slow via Jenkins(SSH or JavaWebStart)
-
wrote on 7 Jan 2019, 12:50 last edited by
I am trying to add an ios project to Jenkins. We have run the command manually on the macos machine physically, but when we use Jenkins to run the same commands, it's painfully slow. We have tried using both ssh login for the slave and using JavaWebStart. The project normally takes 10 to 15 minutes to complete when run locally, but is taking 1 hour 30 minutes when run via Jenkins.
Anyone can give me pointers as to what could be affecting the speed?
-
wrote on 7 Jan 2019, 13:52 last edited by
The Jenkins instance is hosted on a different server and is currently connected to several linux slaves that build properly. It's just the macos slave that has the issue.
It seems to be slow in both qmake and make steps.
We just found a solution that requires us to switch the user to itself before running the command.
sudo -u <loggedinuser> -i bash /script/containging/build/commands.shI'm not sure why this has to be done since we are already logged in as the user that we are switching to. My guess is that Apple enables certain restrictions for remote users.
-
I am trying to add an ios project to Jenkins. We have run the command manually on the macos machine physically, but when we use Jenkins to run the same commands, it's painfully slow. We have tried using both ssh login for the slave and using JavaWebStart. The project normally takes 10 to 15 minutes to complete when run locally, but is taking 1 hour 30 minutes when run via Jenkins.
Anyone can give me pointers as to what could be affecting the speed?
@sam_albuquerque What do you use in Jenkins to build the app (is it a virtual machine)? Did you check what exactly takes time there (is it qmake or make)?
-
wrote on 7 Jan 2019, 13:52 last edited by
The Jenkins instance is hosted on a different server and is currently connected to several linux slaves that build properly. It's just the macos slave that has the issue.
It seems to be slow in both qmake and make steps.
We just found a solution that requires us to switch the user to itself before running the command.
sudo -u <loggedinuser> -i bash /script/containging/build/commands.shI'm not sure why this has to be done since we are already logged in as the user that we are switching to. My guess is that Apple enables certain restrictions for remote users.
1/3