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

GitHub Push always builds if workspace is on offline slave node

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • github-plugin
    • None

      If you have a slave node that goes offline when idle that holds the workspace of a build, any GitHub push automatically triggers a build with the message:

      Started on May 24, 2013 8:15:43 PM
      Workspace is offline.
      Scheduling a new build to get a workspace. (nonexisting_workspace)
      Done. Took 1 ms
      Changes found

      Two issues here:

      1. If the job is triggered by a "Test Hook" call from GitHub and the slave is offline, it was always make a build job even if the there isn't any changes.
      2. (unconfirmed but very likely) The job would build even if the branch it is supposed to build isn't the one that was updated because of the "nonexisting_workspace" error.

      This could be resolved if all the tracking took place on the master node.

      Thank you for your consideration.

          [JENKINS-18079] GitHub Push always builds if workspace is on offline slave node

          Joseph Lawson created issue -
          Joseph Lawson made changes -
          Description Original: If you have a slave node that goes offline when idle that holds the workspace of a build, any GitHub push automatically triggers a build with the message:

          {quote}
          Started on May 24, 2013 8:15:43 PM
          Workspace is offline.
          Scheduling a new build to get a workspace. (nonexisting_workspace)
          Done. Took 1 ms
          Changes found
          {quote}

          Two issues here:

          # If the job is triggered by a "Test Hook" call from GitHub and the slave is offline, it was always make a build job even if the there isn't any changes.
          # (unconfirmed but very likely) The job would build even if the branch it is supposed to build isn't the one that was updated because of the "nonexisting_workspace" error.

          Thank you for your consideration.

          I would like to propose that the status of the
          New: If you have a slave node that goes offline when idle that holds the workspace of a build, any GitHub push automatically triggers a build with the message:

          {quote}
          Started on May 24, 2013 8:15:43 PM
          Workspace is offline.
          Scheduling a new build to get a workspace. (nonexisting_workspace)
          Done. Took 1 ms
          Changes found
          {quote}

          Two issues here:

          # If the job is triggered by a "Test Hook" call from GitHub and the slave is offline, it was always make a build job even if the there isn't any changes.
          # (unconfirmed but very likely) The job would build even if the branch it is supposed to build isn't the one that was updated because of the "nonexisting_workspace" error.

          Thank you for your consideration.
          Joseph Lawson made changes -
          Description Original: If you have a slave node that goes offline when idle that holds the workspace of a build, any GitHub push automatically triggers a build with the message:

          {quote}
          Started on May 24, 2013 8:15:43 PM
          Workspace is offline.
          Scheduling a new build to get a workspace. (nonexisting_workspace)
          Done. Took 1 ms
          Changes found
          {quote}

          Two issues here:

          # If the job is triggered by a "Test Hook" call from GitHub and the slave is offline, it was always make a build job even if the there isn't any changes.
          # (unconfirmed but very likely) The job would build even if the branch it is supposed to build isn't the one that was updated because of the "nonexisting_workspace" error.

          Thank you for your consideration.
          New: If you have a slave node that goes offline when idle that holds the workspace of a build, any GitHub push automatically triggers a build with the message:

          {quote}
          Started on May 24, 2013 8:15:43 PM
          Workspace is offline.
          Scheduling a new build to get a workspace. (nonexisting_workspace)
          Done. Took 1 ms
          Changes found
          {quote}

          Two issues here:

          # If the job is triggered by a "Test Hook" call from GitHub and the slave is offline, it was always make a build job even if the there isn't any changes.
          # (unconfirmed but very likely) The job would build even if the branch it is supposed to build isn't the one that was updated because of the "nonexisting_workspace" error.

          This could be resolved if all the tracking took place on the master node.

          Thank you for your consideration.
          Kanstantsin Shautsou made changes -
          Assignee New: Kanstantsin Shautsou [ integer ]
          Kanstantsin Shautsou made changes -
          Link New: This issue is related to JENKINS-30345 [ JENKINS-30345 ]
          Kanstantsin Shautsou made changes -
          Link New: This issue depends on JENKINS-30345 [ JENKINS-30345 ]
          Kanstantsin Shautsou made changes -
          Link Original: This issue is related to JENKINS-30345 [ JENKINS-30345 ]
          Kanstantsin Shautsou made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 149376 ] New: JNJira + In-Review [ 193094 ]

            integer Kanstantsin Shautsou
            joekiller Joseph Lawson
            Votes:
            13 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: