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

Using JNLP slave offers no way to increase memory

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • remoting
    • None
    • Platform: All, OS: All

      It would be nice if Hudson would allow configuring the memory of the slave
      process itself. The slave process does the svn checkout, and this is running
      out of memory for us, for large repositories (which is possibly a problem in its
      own right - a svn checkout should not need to hold onto so much memory!)

      Ideally it would be good if this could be somewhere near the slave
      configuration, but it seems to me that it would need to be the same value for
      all slaves.

      Initially the workaround for this issue is to put max-heap-size="200M" oni each
      <j2se> element in slave-agent.jnlp.jelly

      Marking as a defect as the net result is that we are unable to build using the
      slaves.

          [JENKINS-3398] Using JNLP slave offers no way to increase memory

          trejkaz created issue -
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 133471 ] New: JNJira + In-Review [ 202185 ]

            Unassigned Unassigned
            trejkaz trejkaz
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: