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

Add way of passing arbitary options to the equinox launchers


    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • buckminster-plugin
    • None

      When I use the buckminster plugin, it generates a command that looks like this (file paths edited for brevity):

      java -Dbuckminster.output.root=/workspace/buckminster.output -Dbuckminster.temp.root=/workspace/buckminster.temp -Xmx256m -jar /buckminster/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar -application org.eclipse.buckminster.cmdline.headless -data /workspace --loglevel debug -S /workspace/commands.txt

      I need one slight change to that. I need the text

        -keyring ~/.gda/.keyring

      inserted AFTER the equinox.launcher.jar, and BEFORE the -application, so that it is an argument to the launcher. So the command should look like:

      ... -jar /buckminster/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar -keyring ~/.gda/.keyring -application  ...

      The problem is, there is no way to do this. There are 2 places to set Buckminsters options, but neither is suitable:

      • In the main Hudson configuration settings, Buckminster supports an "Additonal Startup Parameters" setting, but this is passed to "java", not to the equinox launcher.
      • In the individual job configuration settings, Buckminster supports a "JVM Arguments" setting (under advanced options), but this is passed to the org.eclipse.buckminster.cmdline.headless application, not to its launcher.

      Would it be possible to add an extra configuration option to the job, as an Advanced option, where one could specify additional launcher arguments (eg -keyring)?

      Wihtout this, I can't use the Buckminster plugin, and will need to code the backminster commands directly in a shell script.

            jutzig jutzig
            mwebber Matthew Webber
            0 Vote for this issue
            0 Start watching this issue