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

Jenkins-Swarm 3.6.0 "No Working Directory. Using the legacy JAR Cache location"

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: swarm-plugin
    • Labels:
      None
    • Environment:
      Debian
    • Similar Issues:

      Description

      Hi guys,

      I have a multi deployment on Azure with Jenkins + Jenkins Swarm agents. I'm currently using Jenkins 2.91.0 and Jenkins-Swarm 3.6.0.

      Each time I start the Jenkins-swarm agent I face this warning in the jenkins-swarm logs:

      No Working Directory. Using the legacy JAR Cache location

      This is not a big issue, but I am not able to remove this warning message changing the fsroot  
      parameter to set another directory of Jenkins-Swarm to use while running.

      I suspect this is due to the latest update of Jenkins-Swarm, which includes this in the changelog: 

       

      Update Remoting in Swarm Client from 3.4.1 to 3.10.2
      

       

      Could anyone point me which is the source of this warning and how could I remove it? As I pointed before, this is not blocking anything, but I would like to remove these kind of warnings.

      Thank you so much, 

      kind regards.

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            JENKINS-44115 should provide support of workDirectories or enable them by default. so far there is no way to get rid of this message AFAICT

            Show
            oleg_nenashev Oleg Nenashev added a comment - JENKINS-44115 should provide support of workDirectories or enable them by default. so far there is no way to get rid of this message AFAICT

              People

              • Assignee:
                oleg_nenashev Oleg Nenashev
                Reporter:
                arp4 David Barranco
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: