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

Introduce the remoting working directory concept

    XMLWordPrintable

Details

    • New Feature
    • Resolution: Fixed
    • Major
    • remoting
    • None

    Description

      Right now remoting has no it's own Working Directory on startup. It complicates implementation of features like JENKINS-39369 and JENKINS-18578

      Requirements:

      • The directory is compatible with the current agent workspace architecture of JNLP slaves and
      • The directory is being created only if explicitly required (behavior compatibility for the current workspace-less agents)
      • The workspace should not interfere with Jenkins plugins putting the data to the root of the agent workspace

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars

          • Major - Major loss of function.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-39369 Automatically dump agent logs to the disk

          • Major - Major loss of function.
          • Resolved
          is blocking

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-39130 Jenkins JNLP agents should not connect/schedule builds if the workspace cannot be created or not writable

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link CloudBees Internal OSS-553

          Web Link remoting/pull/129

          Activity

            People

              oleg_nenashev Oleg Nenashev
              oleg_nenashev Oleg Nenashev
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: