• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 3993 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Building CCS Project using Jenkins -

tamo2
Expert 1670 points
Other Parts Discussed in Thread: CCSTUDIO

Hi,

I am trying to build a CCS project from Jenkins.
Here is the script I use:

echo -- Start Buiding --
/opt/ti/ccsv5/eclipse/eclipse -noSplash -data "/home/slroot/sl/trunk/workspace" -application com.ti.ccstudio.apps.projectBuild -ccs.configuration Release -ccs.projects slif_dsp
echo -- End Building --

If I run the script from a Console, it builds fine, but if run from Jenkins, it gets the following error:

org.eclipse.core.runtime.CoreException: Plug-in com.ti.ccstudio.project.core was unable to load class com.ti.ccstudio.project.core.internal.variables.CCSPathVariableResolver__INSTALL_ROOT.

I attached the entire log.  Jenkins' user is set to the same user as the one I build from Console.

CCS 5.1.0.09000
Ubuntu 10.04.04
Jenkins  1.477

Can anybody tell what is wrong?

Thanks!

  • 0
    TI__Prodigy 130 points

    Hello tamo2,

    The log files are ultimately showing that the errors are caused here:

    Caused by: org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
    at org.eclipse.swt.SWT.error(SWT.java:4308)
    at org.eclipse.swt.widgets.Display.createDisplay(Display.java:909)
    at org.eclipse.swt.widgets.Display.create(Display.java:897)
    at org.eclipse.swt.graphics.Device.<init>(Device.java:157)
    at org.eclipse.swt.widgets.Display.<init>(Display.java:500)
    at org.eclipse.swt.widgets.Display.<init>(Display.java:491)
    at org.eclipse.swt.widgets.Display.getDefault(Display.java:1681)

    where the Jenkins user is unable to create a display as it does not have its own open X session.  (I believe this works for you since of course you do have an X session when running from the console, whereas a Jenkins job will not irrespective of the same user account being used.)

    There is some discussion from people who have encountered this general issue (note: same error message) here. https://groups.google.com/forum/?fromgroups#!topic/google-web-toolkit/oputV8DJImg%5B1-25%5D

    I think that you would need to modify your Jenkins job to create a virtual framebuffer and set the DISPLAY variable to point to that before attempting to launch eclipse, such that a graphical environment would be available for your job during execution.

    Cheers.

  • 0 in reply to AF
    Expert 1670 points

    Hi AF,

    Thanks for the reply and for the detailed analysis.  Now I see why it was causing the problem.
    I have already implemented a workaround by using named pipes, but I will revisit this when next time I setup Jenkins.

    Thanks so much!