Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-3970

Unable to launch the Synergy client on a UNIX slave

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • synergy-plugin
    • None
    • Platform: Other, OS: All

      Not sure whether this is a bug report or the plugin is working as intended in
      which case this is an enhancement request to support both Windows and UNIX
      Synergy clients. But in a nutshell I am unable to find a way of configuring the
      plugin to launch a Synergy client on UNIX when our Hudson master node is
      Windows.

      Our organisation is using Telelogic Synergy hosted on a Sun server with
      both UNIX and Windows clients to manage a multi-platform product. Our
      Hudson system is installed on a Windows server. We are currently using the
      Synergy SCM plug-in to do continuous builds on Windows and this is working
      extremely well. However, we also wish to run builds on an AIX machine because
      the compiler on this machine flags errors that compilers on other servers
      do not. However, I cannot get the plug-in to start Synergy on the UNIX
      box.

      If I just allow the name of the Synergy executable to default to 'ccm' on
      the main Hudson configuration page then I get the error that the ccm
      executable cannot be found on the path when I run a job that is configured
      to invoke the Synergy plug-in on an AIX slave. I have configured the slave
      node that this job runs on so that the Synergy bin directory is on the
      path and if I run a test Hudson job on this slave that merely prints the
      environment, the PATH is indeed set correctly. It is as though the plug-in
      does not see this same environment when launching Synergy on the slave.

      If I try to configure the full path to the ccm executable, then an error
      message appears on the Hudson configuration page that complains that the
      executable cannot be found. From the path that is displayed as part of
      this error message, it is as though the plug-in is only allowing Windows
      pathnames to be entered.

            jribette jribette
            swbarry swbarry
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: