• 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

          Oleg Nenashev added a comment -

          Duplicates JENKINS-4960

          Oleg Nenashev added a comment - Duplicates JENKINS-4960

          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.

          Oleg Nenashev added a comment -

          Reverted the status. I just imagine a plugin with several checkboxes for masters and slaves, hence these issues have a similar implementation for me.

          You're right that feature requests are different in general

          Oleg Nenashev added a comment - Reverted the status. I just imagine a plugin with several checkboxes for masters and slaves, hence these issues have a similar implementation for me. You're right that feature requests are different in general

          Can this be reopened? There are other issues that had been closed as duplicates of this, and this one is closed. I see it if not a bug, then a huge oversight that there is not a checkbox for whether master should do an SCM checkout as well. I am in the exact same boat as Alexander, the master does a lengthy unnecessary SCM checkout before the slaves start building. I tried to work around this by using a custom workspace for the slaves and reuse it from the master, but the workspace name can not be constructed from the axis values as they are not initialised there yet. The current behaviour is 1) unexpected 2) increases build times by tens of percent for no gain. What good does it do to do two SCM syncs, where one is discarded?

          Tommi Kiviniemi added a comment - Can this be reopened? There are other issues that had been closed as duplicates of this, and this one is closed. I see it if not a bug, then a huge oversight that there is not a checkbox for whether master should do an SCM checkout as well. I am in the exact same boat as Alexander, the master does a lengthy unnecessary SCM checkout before the slaves start building. I tried to work around this by using a custom workspace for the slaves and reuse it from the master, but the workspace name can not be constructed from the axis values as they are not initialised there yet. The current behaviour is 1) unexpected 2) increases build times by tens of percent for no gain. What good does it do to do two SCM syncs, where one is discarded?

          Daniel Beck added a comment -

          Can this be reopened? There are other issues that had been closed as duplicates of this, and this one is closed.

          This has been reopened in late 2014 and not closed since.

          Daniel Beck added a comment - Can this be reopened? There are other issues that had been closed as duplicates of this, and this one is closed. This has been reopened in late 2014 and not closed since.

          Sven K added a comment -

          Can't this be resolved somehow? In combination with this JENKINS-22494 and a lot of slave machines, this is pretty annoying, since a random slave is used and repositories are checked out there (which takes up disk space). Is there a workaround?

          Sven K added a comment - Can't this be resolved somehow? In combination with this JENKINS-22494 and a lot of slave machines, this is pretty annoying, since a random slave is used and repositories are checked out there (which takes up disk space). Is there a workaround?

          Is there any way to to force fix for this issue?

          We have huge repository with multiple branches, this additional checkout significantly increases build time.

          Eugeny Napalkov added a comment - Is there any way to to force fix for this issue? We have huge repository with multiple branches, this additional checkout significantly increases build time.

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

              Created:
              Updated: