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

when an agent goes offline the workspace for a build defaults to an older available build on a different agent

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None
    • windows and linux

      i have configured a set of slaves to go offline as un-needed. a build job (buildJobA) has occurred on buildSlaveA and creates/leaves a successful workspace on the slave. A later in time build of buildJobA fires up buildSlaveB and successfully builds on buildSlaveB leaving a current and newer workspace on buildSlaveB.

      Time and demand passes and buildSlaveB goes off line. Now select buildJobA on Jenkins and browse the workspace, you will be sent to the old build workspace on the "still up" buildSlaveA. This results in beatings for the build guy cause "you aren't pulling/building the latest stuff", even though the build guy shows the dev's that the good stuff IS on the buildSlaveB workspace via rdp/vnc.

      suggestion:
      either bring the sleeping slave on line to get to the latest workspace
      OR
      display some sort of warning about viewing and old workspace.

          [JENKINS-9898] when an agent goes offline the workspace for a build defaults to an older available build on a different agent

          Kohsuke Kawaguchi added a comment -

          I think the right fix is to bind "some workspace" separately from the latest workspace under different URLs. Clicking the workspace link when it's non-existent should result in a warning page that navigates the user to the stale workspace URL.

          (Or it should silently transfer to the stale URL to keep the existing program clients working, and just have some warning message on top indicating it being stale.)

          Kohsuke Kawaguchi added a comment - I think the right fix is to bind "some workspace" separately from the latest workspace under different URLs. Clicking the workspace link when it's non-existent should result in a warning page that navigates the user to the stale workspace URL. (Or it should silently transfer to the stale URL to keep the existing program clients working, and just have some warning message on top indicating it being stale.)

            Unassigned Unassigned
            sbrinkmeyer sbrinkmeyer
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: