• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • other
    • None
    • Platform: All, OS: All

      Please, allow matrix jobs to run sequentially by clicking a checkbox.

      That will allow to easily work with matrixes that for one reason or another
      cannot run in parallel (shared resources). Fixing locks in hudson will fix as
      well but I think this will be generally useful.

      It is just like the option for the Native Maven projects so why not have the
      same in Matrix projects?

          [JENKINS-3028] Matrix builds to run optionally sequentially

          akostadinov added a comment -

          changing to enhancement

          akostadinov added a comment - changing to enhancement

          igilany added a comment -

          Created an attachment (id=819)
          patch

          igilany added a comment - Created an attachment (id=819) patch

          Code changed in hudson
          User: : kohsuke
          Path:
          trunk/hudson/main/core/src/main/java/hudson/matrix/MatrixBuild.java
          trunk/hudson/main/core/src/main/java/hudson/matrix/MatrixConfiguration.java
          trunk/hudson/main/core/src/main/java/hudson/matrix/MatrixProject.java
          trunk/hudson/main/core/src/main/java/hudson/model/Queue.java
          trunk/hudson/main/core/src/main/resources/hudson/matrix/MatrixProject/configure-entries.jelly
          trunk/hudson/main/core/src/main/resources/hudson/matrix/MatrixProject/help-runSequentially.html
          trunk/www/changelog.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=20445
          Log:
          [FIXED JENKINS-3028] in 1.319. In a long run, I believe doing this control in the queue with ResourceController is better, because (1) scheduling one at a time can create unnecessary wait time — say if one of the configuration needs to run on a slave that's blocked, then it's better to schedule others first, and (2) the notion of shared resources spans beyond a single job, so doing that coordination at a job level isn't general enough. That said, I think it'll be easy enough to maintain data compatibility when this happens, so I'm committing this change now.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : kohsuke Path: trunk/hudson/main/core/src/main/java/hudson/matrix/MatrixBuild.java trunk/hudson/main/core/src/main/java/hudson/matrix/MatrixConfiguration.java trunk/hudson/main/core/src/main/java/hudson/matrix/MatrixProject.java trunk/hudson/main/core/src/main/java/hudson/model/Queue.java trunk/hudson/main/core/src/main/resources/hudson/matrix/MatrixProject/configure-entries.jelly trunk/hudson/main/core/src/main/resources/hudson/matrix/MatrixProject/help-runSequentially.html trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=20445 Log: [FIXED JENKINS-3028] in 1.319. In a long run, I believe doing this control in the queue with ResourceController is better, because (1) scheduling one at a time can create unnecessary wait time — say if one of the configuration needs to run on a slave that's blocked, then it's better to schedule others first, and (2) the notion of shared resources spans beyond a single job, so doing that coordination at a job level isn't general enough. That said, I think it'll be easy enough to maintain data compatibility when this happens, so I'm committing this change now.

            Unassigned Unassigned
            akostadinov akostadinov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: