12

I am using Xcode 6.1. And i need to run a UI automation script from jenkins as a post build action. The command that i use is shown below.

instruments -t $TRACETEMPLATE -w $DEVICE $APP_PATH -e UIASCRIPT $SCRIPT -e UIARESULTSPATH $RESULTS_PATH | grep "<"  > test-reports/test-results.xml

When i run that the following error is thrown by jenkins.

Failed to authorize rights (0x1) with status: -60007. 2014-11-12 16:31:30.685 instruments[488:2607] -[XRSimulatorDevice prepareConnection:]: Unable to authorize simulated daemon (99637): 8 Instruments Trace Error : Target failed to run: Permission to debug com.test.app was denied.

Any help is much appreciated.

Lrenger semigo
  • 243
  • 2
  • 9
  • I had similar issues with Jenkins on remote server. The user permissions to access resources must be same as the ones on your local PC. – ekostadinov Nov 13 '14 at 13:47
  • Did you get this working? Please post the answer. I'm having the same problem right now, too. I can run the same command that Jenkins runs by pasting it into Terminal, but it fails with the same error as yours when launched by Jenkins. – bugloaf Apr 24 '15 at 22:02

3 Answers3

1

  1. The user that invokes Instruments must have developer permissions. The user must be in the _developer group.

  2. Security permissions allowing the user to access Instruments must be set. See the man page for DevToolsSecurity

  3. The user must be logged in to a window server to use the simulator. How to do this will depend somewhat on your Jenkins and OS configuration for that user. In older versions of MacOS creating an SSH connection back into the machine and running Instruments through that connection typically worked. YMMV.

Note that any of the above steps escalates the rights for the Jenkins user, which was security implications.

quellish
  • 21,123
  • 4
  • 76
  • 83
0

I got an almost identical error message to yours, and it seemed to be because when Jenkins is launched as a Launch Daemon, it doesn't have access to the screen, even if you log in as "jenkins".

I found the solution from reading this discussion: https://issues.jenkins-ci.org/browse/JENKINS-14421

You can either launch Jenkins from Terminal with java -jar jenkins.war, or you can create a Launch Agent, which runs as the logged-in user and has access to the user's screen.

I achieved the latter solution by moving /Library/LaunchDaemons/org.jenkins-ci.plist to /Library/LaunchAgents/org.jenkins-ci.plist and removing the UserName key and value from the plist. Now Jenkins doesn't start automatically when I boot the machine, but it does start when I log into the desktop, which is required for running UI Automation tests anyway.

It appears that Jenkins still can't actually launch the Simulator app, but if Simulator is already running, the UI Automation scripts proceed just fine.

bugloaf
  • 2,890
  • 3
  • 30
  • 49
0

I also got this error message. Moving service from LaunchDaemons to LaunchAgents didn't solve the problem. My solution was as following:

  1. remove the service by deleting /Library/LaunchAgents/org.jenkins-ci.plist file

  2. create an iOS application using Automator tool. (Which I think exists by default):

    • I chose "Library" -> "Utilities" -> "Shell Script".
    • Enter the content of /Library/Application Support/Jenkins/jenkins-runner.sh.
    • Put export JENKINS_HOME=/path/to/jenkins at the top.
    • Save the app somewhere

  3. Go to Preferences -> Users & Groups -> choose your user -> Add the saved app.

This way, jenkins is run as an application after login and it has all the privilages of any other application.

Esenbek Kydyr uulu
  • 1,553
  • 1
  • 14
  • 19