| Failing to perform headless build via jenkins on a non-gui server [message #1829738] |
Thu, 09 July 2020 20:05 |
 Ilya Frumson
Messages: 1
Registered: July 2020 |
Junior Member |
|
|
Hi,
In my company,we are trying to implement continuous integratio using eclipse-based CDT toolbox (the issue below happens with eclipse Mars and Neon versions - didn't yet check newer versions since it requires some installation that was not yet done succesfully due to several reasons).
We are trying to compile an eclipse C project from command line via jenkins, using eclipse headless build. The jenkins slave is Ubuntu 16.04.5 LTS server without gui support (jenkins connects to it via ssh). Jenkins version: 2.176.1
However, we receive an error: "Failed to connect to Mir: Failed to connect to socket: No sich file or directory. Unable to init server: could not connect: connectiom refused".
After a very long investigation we found that the root cause of the issue is the fact that the headless build requires a gui support to display the splash screen during the run. This is the case even when running with -nosplash flag - the splash screen is not displayed but if a gui support is not present,the same error occurs.
So far the best solution we found is redirecting the splash screen to a machine that does have gui support (via export DISPLAY=machine-name:session id).However this solution is not good for real continuous integration,since session id changes each time the session terminates,and effectively this means we need to keep the session alive on the other machine just for this reason.
Is this a known issue resolved in some newer version? Or I should open a bug to eclipse?
Thanks!
|
|
|
Powered by
FUDForum. Page generated in 0.03370 seconds
] 
Search
Help
Register
Login
Home
