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

ignore the checkout on the master

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • matrix-project-plugin
    • None
    • all

      in a Matrix job , we need to ability to ignore the checkout on the Master.

          [JENKINS-14618] ignore the checkout on the master

          morlajb created issue -
          Jenkins IRC Bot made changes -
          Component/s New: matrix-project [ 18765 ]
          Component/s Original: matrix [ 15501 ]
          Oleg Nenashev made changes -
          Link New: This issue duplicates JENKINS-4960 [ JENKINS-4960 ]

          Oleg Nenashev added a comment -

          Duplicates JENKINS-4960

          Oleg Nenashev added a comment - Duplicates JENKINS-4960
          Oleg Nenashev made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Daniel Beck added a comment -

          Oleg: I disagree, the other wants 1 SCM checkout, this one wants N checkouts, instead of N+1. This one is actually the exact opposite of JENKINS-4960. They're related, but not duplicate IMO.

          Daniel Beck added a comment - Oleg: I disagree, the other wants 1 SCM checkout, this one wants N checkouts, instead of N+1. This one is actually the exact opposite of JENKINS-4960 . They're related, but not duplicate IMO.

          Alexander Ziller added a comment - - edited

          I have a similar case:

          I have a multi-configuration Job that has to run on multiple nodes at the same time. I want the job to checkout from CVS, then do build steps on the CVS content.
          Current situation
          -Multiple slave nodes are assigned to the job.
          -Master is NOT assigned to the job.
          -CVS is accessed by pserver CVSROOT and defined in the job configuration
          Current behaviour
          -Master checks out from CVS, then delegates job to the slave nodes, which also do a CVS checkout, then do the job
          Expected behaviour
          -Master immediately delegates to the assigned nodes without doing a CVS chekout first. Since the master is not an assigned node of the job, it is not supposed to do anything concerning the job.

          Alexander Ziller added a comment - - edited I have a similar case: I have a multi-configuration Job that has to run on multiple nodes at the same time. I want the job to checkout from CVS, then do build steps on the CVS content. Current situation -Multiple slave nodes are assigned to the job. -Master is NOT assigned to the job. -CVS is accessed by pserver CVSROOT and defined in the job configuration Current behaviour -Master checks out from CVS, then delegates job to the slave nodes, which also do a CVS checkout, then do the job Expected behaviour -Master immediately delegates to the assigned nodes without doing a CVS chekout first. Since the master is not an assigned node of the job, it is not supposed to do anything concerning the job.
          Alexander Ziller made changes -
          Link New: This issue is related to JENKINS-25040 [ JENKINS-25040 ]
          Oleg Nenashev made changes -
          Link Original: This issue duplicates JENKINS-4960 [ JENKINS-4960 ]
          Oleg Nenashev made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

            Unassigned Unassigned
            morlajb morlajb
            Votes:
            15 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated: