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

Introduce the remoting working directory concept

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: remoting
    • Labels:
      None
    • Similar Issues:

      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

            Activity

            oleg_nenashev Oleg Nenashev created issue -
            oleg_nenashev Oleg Nenashev made changes -
            Field Original Value New Value
            Epic Link JENKINS-38833 [ 175240 ]
            oleg_nenashev Oleg Nenashev made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue blocks JENKINS-39369 [ JENKINS-39369 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue blocks JENKINS-18578 [ JENKINS-18578 ]
            oleg_nenashev Oleg Nenashev made changes -
            Description Right now remoting has no it's own Working Directory on startup. It complicates implementation of features like JENKINS-39369 and JENKINS-18578 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
            oleg_nenashev Oleg Nenashev made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is blocking JENKINS-39130 [ JENKINS-39130 ]
            recampbell Ryan Campbell made changes -
            Comment [ Oleg, you've marked this as In Review, but none of the issues link to any PR. ]
            oleg_nenashev Oleg Nenashev made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "remoting/pull/129 (Web Link)" [ 15091 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Link JENKINS-38833 [ 175240 ] JENKINS-44108 [ 181734 ]
            oleg_nenashev Oleg Nenashev made changes -
            Status In Review [ 10005 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            cloudbees CloudBees Inc. made changes -
            Remote Link This issue links to "CloudBees Internal OSS-553 (Web Link)" [ 18878 ]

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: