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

Configuration Matrix combination filter ignored

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core

      I'm attempting to configure a job that should run on several machines with differing compilers. My machines have OS-related labels (i.e., linux.rh.5, linux.rh.6) as well as supported compiler labels (i.e., gcc-4.5.3, etc.).

      Attached is a screenshot of my matrix settings, where I'm selecting three different compiler labels and two different OS labels and I'm attempting to use a combination filter in order to not attempt a label combination of linux.rh.6 and gcc-3.4.6, but allow all other combinations.

      After saving these settings, the combination matrix view available in the job page gives me a gray ball for the combination I want to weed out, however, as shown below, the job is hung attempting the combination anyway.

      Started by user someUser
      Building on master in workspace /var/lib/jenkins/jobs/Test.Job/workspace
      Triggering gcc-4.5.3,linux.rh.5
      Triggering gcc-4.5.3,linux.rh.6
      Triggering gcc-3.4.6,linux.rh.5
      Triggering gcc-4.6.3,linux.rh.5
      Triggering gcc-4.6.3,linux.rh.6
      Triggering gcc-3.4.6,linux.rh.6
      gcc-4.5.3,linux.rh.5 completed with result SUCCESS
      gcc-4.5.3,linux.rh.6 completed with result SUCCESS
      gcc-3.4.6,linux.rh.5 completed with result SUCCESS
      gcc-4.6.3,linux.rh.5 completed with result SUCCESS
      gcc-4.6.3,linux.rh.6 completed with result SUCCESS
      Configuration gcc-3.4.6,linux.rh.6 is still in the queue: All nodes of label 'gcc-3.4.6&&linux.rh.6' are offline
      Aborted
      Aborted by someUser
      Cancelled gcc-3.4.6,linux.rh.6
      Finished: ABORTED
      

          [JENKINS-14152] Configuration Matrix combination filter ignored

          Changed priority to Critical

          David Ehrenberger added a comment - Changed priority to Critical

          Upgrading from 1.475 to 1.481 has resolved this defect. This can be closed.

          David Ehrenberger added a comment - Upgrading from 1.475 to 1.481 has resolved this defect. This can be closed.

          Closing as user confirmed that after upgrading from 1.475 to 1.481 the issue disappeared.

          Bruno P. Kinoshita added a comment - Closing as user confirmed that after upgrading from 1.475 to 1.481 the issue disappeared.

            Unassigned Unassigned
            daehren David Ehrenberger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: