Skip to content

[JENKINS-28111] JNLP slave JVM Options are inconsistently applied #21068

Closed
Bug
Closed
[JENKINS-28111] JNLP slave JVM Options are inconsistently applied#21068
Bug
Labels
component:coreimported-jira-issuepriority:minorresolution:fixed

Description

@jenkins-infra-bot
jenkins-infra-bot
opened on Apr 27, 2015

The JVM Options are injected into the JNLP file as the java-vm-args attribute but the command line launch option does not reflect the requirements for JVM Options.

The "Run from slave command line" option should include the specified JVM options for the non-javaws varietals.

Originally reported by stephenconnolly, imported from: JNLP slave JVM Options are inconsistently applied
  • assignee: stephenconnolly
  • status: Closed
  • priority: Minor
  • component(s): core
  • resolution: Fixed
  • resolved: 2015-04-27T21:40:48+00:00
  • votes: 0
  • watchers: 3
  • imported: 2025-11-24
Raw content of original issue 
The JVM Options are injected into the JNLP file as the java-vm-args attribute but the command line launch option does not reflect the requirements for JVM Options.



The "Run from slave command line" option should include the specified JVM options for the non-javaws varietals.

Activity

  1. jenkins-infra-bot commented on Apr 27, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on Apr 27, 2015
    Author
    danielbeck:
    • Original comment link
    • Raw content of original comment: 
      I'm fairly sure this has been reported before (or was that for the installed slave service on Windows?)

    I'm fairly sure this has been reported before (or was that for the installed slave service on Windows?)

  2. jenkins-infra-bot commented on Apr 27, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on Apr 27, 2015
    Author
    stephenconnolly:
    • Original comment link
    • Raw content of original comment: 
      Installed service for windows was reported previously. Nobody from what I could find had reported that the displayed command line launch alternative did not include the JVM options

    Installed service for windows was reported previously. Nobody from what I could find had reported that the displayed command line launch alternative did not include the JVM options

  3. jenkins-infra-bot commented on Apr 27, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on Apr 27, 2015
    Author
    danielbeck:

    stephenconnolly Should this be assigned to you?

  4. jenkins-infra-bot commented on Apr 27, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on Apr 27, 2015
    Author
    scm_issue_link:

    Code changed in jenkins
    User: Stephen Connolly
    Path:
    core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly
    http://jenkins-ci.org/commit/jenkins/84e485fc5e608bccf080bf46c0e31c43c6bef474
    Log:
    [FIXED JENKINS-28111] JNLP slave JVM Options are inconsistently applied

  5. jenkins-infra-bot
    closed this as completedon Apr 27, 2015

  6. jenkins-infra-bot commented on Apr 27, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on Apr 27, 2015
    Author
    scm_issue_link:

    Code changed in jenkins
    User: Stephen Connolly
    Path:
    core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly
    http://jenkins-ci.org/commit/jenkins/ce94434b164d1ac74132cecdc6f123787decbf48
    Log:
    Merge pull request #1676 from stephenc/jenkins-28111

    [FIXED JENKINS-28111] JNLP slave JVM Options are inconsistently applied

    Compare: 5b4ed2d...ce94434

  7. jenkins-infra-bot commented on Apr 27, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on Apr 27, 2015
    Author
    scm_issue_link:

    Code changed in jenkins
    User: Stephen Connolly
    Path:
    changelog.html
    http://jenkins-ci.org/commit/jenkins/9c9049eb4da6145261d6b5fda6ed57dd676bf108
    Log:
    Noting merge of JENKINS-28111

  8. jenkins-infra-bot commented on Apr 29, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on Apr 29, 2015
    Author
    dogfood:

    Integrated in jenkins_main_trunk #4114

    Result = SUCCESS

  9. jenkins-infra-bot commented on May 15, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 15, 2015
    Author
    scm_issue_link:
    • Original comment link
    • Raw content of original comment: 
      Code changed in jenkins
User: tfennelly
Path:
 changelog.html
 cli/pom.xml
 core/pom.xml
 core/src/main/java/hudson/model/Executor.java
 core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly
 ips/jenkins.xml
 ips/proto.py
 ips/readme.txt
 plugins/pom.xml
 pom.xml
 test/pom.xml
 war/pom.xml
http://jenkins-ci.org/commit/jenkins/30ece5ffb20d354173cec3b6d7a2ea902a9eb681
Log:
  Merge branch 'master' into extensionlist-listener
      


        
	
      • master:
  Noting merge of JENKINS-28111
  @jglick wants it this way
  Noting merge of JENKINS-28115
  [FIXED JENKINS-28115] Division by zero in Executor.getProgress()
  [FIXED JENKINS-28111] JNLP slave JVM Options are inconsistently applied
  updated changelog for release
  [maven-release-plugin] prepare for next development iteration
  [maven-release-plugin] prepare release jenkins-1.611
  remove ips profile
  Now that packaging is in https://github.com/jenkinsci/packaging and given that the ips packaging is stale, we should just drop this
        •

    Code changed in jenkins
    User: tfennelly
    Path:
    changelog.html
    cli/pom.xml
    core/pom.xml
    core/src/main/java/hudson/model/Executor.java
    core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly
    ips/jenkins.xml
    ips/proto.py
    ips/readme.txt
    plugins/pom.xml
    pom.xml
    test/pom.xml
    war/pom.xml
    http://jenkins-ci.org/commit/jenkins/30ece5ffb20d354173cec3b6d7a2ea902a9eb681
    Log:
    Merge branch 'master' into extensionlist-listener

    • master:
      Noting merge of JENKINS-28111
      @​jglick wants it this way
      Noting merge of JENKINS-28115
      [FIXED JENKINS-28115] Division by zero in Executor.getProgress()
      [FIXED JENKINS-28111] JNLP slave JVM Options are inconsistently applied
      updated changelog for release
      [maven-release-plugin] prepare for next development iteration
      [maven-release-plugin] prepare release jenkins-1.611
      remove ips profile
      Now that packaging is in https://github.com/jenkinsci/packaging and given that the ips packaging is stale, we should just drop this
  10. jenkins-infra-bot
    added
    bugFor changelog: Minor bug. Will be listed after features
    imported-jira-issue
    component:core
    priority:minor
    resolution:fixed
    on Nov 24, 2025
  11. jenkins-infra-bot
    added the
    Bug
    issue type on Nov 25, 2025
  12. jenkins-infra-bot
    removed
    bugFor changelog: Minor bug. Will be listed after features
    on Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    component:coreimported-jira-issuepriority:minorresolution:fixed

    Type

    Bug

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions