Build Unity project with Jenkins failed

Question

I'm trying to build Unity project with Jenkins on Mac OS Server. But when I try to run the following script

/Applications/Unity/Unity.app/Contents/MacOS/Unity -quit -batchmode ${PROJECT_PATH} -executeMethod BuildScript.DevelopmentBuild

The script shows this,

_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.

Does anyone knows how to fix the problem?

Internalize

Now I fixed the problem. I moved Jenkins CI from /Library/LaunchDaemons/ to /Library/LaunchAgents/. Also I made jenkins user and install Unity3D on jenkins user. Then keep logged in jenkins user. – Internalize

Answer 1

Try write from Terminal:

sudo launchctl unload /Library/LaunchDaemons/org.jenkins-ci.plist
sudo mv /Library/LaunchDaemons/org.jenkins-ci.plist /Library/LaunchAgents/org.jenkins-ci.plist

Then log out and log in again.

Now Jenkins will run as agent and can access WindowServer.

Supersaturate

I had to restart my machine after this change. Logging out and logging in wasn't enough. Also I don't have Jenkins configured to run on machine startup, so I had to run sudo launchctl load /Library/LaunchAgents/org.jenkins-ci.plist after restarting. – Millian

Did also had to restart the machine, but after that it just worked fine! thx – Pathognomy

Answer 2

Make sure you have -nographics parameter among your startup parameters

Selfesteem

Answer 3

I tried

sudo launchctl unload /Library/LaunchDaemons/org.jenkins-ci.plist

sudo mv /Library/LaunchDaemons/org.jenkins-ci.plist /Library/LaunchAgents/org.jenkins-ci.plist

Then Restarted my Mac

And then sudo launchctl load /Library/LaunchAgents/org.jenkins-ci.plist after restarting

It worked

Tetany

Answer 4

I had this same issue. The problem is with how Jenkins and Unity work individually. The only way I could find a cleaner work around was:

1. Ideally have your Jenkins master only do assignments to slave and do not build anything by itself. So your slaves would build the project.
2. In case above is not easily doable here is a quick workaround:
   • On your Jenkins master create a slave.
   • Add a label to execute your Unity project on the newly created slave.
   • Configure the job to run on dedicated slave that you created above.
   • All works now!

Hypotonic

Answer 5

You also get this error if the user you are running as is not currently logged in graphically.

Forge

Answer 6

It looks like you're missing the --projectPath option prior to specifying your project's path?

Executioner

I tried with --projectPath option as Unity -batchmode -quit -projectPath "${UNITY_PROJECT_PATH}" -executeMethod BuildScript.DevelopmentBuild. But won't build. – Internalize