Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-9351

Jenkins redirecting to incorrect build numbers

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Continuous Integration
    • Labels:
      None

      Description

      Consider lsst_py3 job #429. This job has a red "failure" marker.

      This claims a "subproject build" of stack-os-matrix #21028. This also has a red "failure" marker.

      stack-os-matrix #21028 lists two configurations (label=centos-6 and label=centos-7). These both have green "success" markers.

      However, clicking through to these configurations takes us to:

      respectively. Note that the job number in the URL has changed, from 21028 to 21027! This is incorrect.

      The correct job to link to is https://ci.lsst.codes/job/stack-os-matrix/label=centos-7,python=py3/21028/.

      Getting redirected to the wrong output when trying to debug CI failures is painful. Please help!

        Attachments

          Issue Links

            Activity

            Hide
            swinbank John Swinbank added a comment -

            (Added both Frossie & Josh as watchers, since JIRA doesn't assign the ticket automatically.)

            Show
            swinbank John Swinbank added a comment - (Added both Frossie & Josh as watchers, since JIRA doesn't assign the ticket automatically.)
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            We've seen this before and I think it may go away after a master restart. I will see if there is an existing jenkins issue or file one. However, it is worth noting that the jenkins devs want folks to replace the matrix job type with pipelines. This is a catch 22 for us as the out of the box jenkins UI is essentially unusable for "multi-branch" pipelines. The new jenkins "blue ocean" UI will solve this problem but doesn't support matrix jobs. Based on discussion on #jenkins, it seems unlikely it ever will. The rough plan is to have a matrix->pipeline flag day in the march/april time frame when blue ocean is out of beta.

            Show
            jhoblitt Joshua Hoblitt added a comment - We've seen this before and I think it may go away after a master restart. I will see if there is an existing jenkins issue or file one. However, it is worth noting that the jenkins devs want folks to replace the matrix job type with pipelines. This is a catch 22 for us as the out of the box jenkins UI is essentially unusable for "multi-branch" pipelines. The new jenkins "blue ocean" UI will solve this problem but doesn't support matrix jobs. Based on discussion on #jenkins, it seems unlikely it ever will. The rough plan is to have a matrix->pipeline flag day in the march/april time frame when blue ocean is out of beta.
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            I think we were seeing an aspect of this upstream issue (double reported):

            https://issues.jenkins-ci.org/browse/JENKINS-30437
            https://issues.jenkins-ci.org/browse/JENKINS-34389

            Show
            jhoblitt Joshua Hoblitt added a comment - I think we were seeing an aspect of this upstream issue (double reported): https://issues.jenkins-ci.org/browse/JENKINS-30437 https://issues.jenkins-ci.org/browse/JENKINS-34389
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            A likely fix has been merged into the matrix-project plugin: https://github.com/jenkinsci/matrix-project-plugin/pull/41

            A release including the PR hasn't been cut yet.

            Show
            jhoblitt Joshua Hoblitt added a comment - A likely fix has been merged into the matrix-project plugin: https://github.com/jenkinsci/matrix-project-plugin/pull/41 A release including the PR hasn't been cut yet.
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            The fix was released as part of https://github.com/jenkinsci/matrix-project-plugin/releases/tag/matrix-project-1.10 on April 19th. A few days or so after that, the production jenkins instance was manually updated to the new release. This appears to have resolved the broken links and a number of other issues that were suspected to be related to dynamic axis/matrix project corruption.

            The plugin version change has been committed to version control and the aggressive PRs to remove usage of dynamic axis plugin have been withdrawn.

            Show
            jhoblitt Joshua Hoblitt added a comment - The fix was released as part of https://github.com/jenkinsci/matrix-project-plugin/releases/tag/matrix-project-1.10 on April 19th. A few days or so after that, the production jenkins instance was manually updated to the new release. This appears to have resolved the broken links and a number of other issues that were suspected to be related to dynamic axis/matrix project corruption. The plugin version change has been committed to version control and the aggressive PRs to remove usage of dynamic axis plugin have been withdrawn.

              People

              • Assignee:
                jhoblitt Joshua Hoblitt
                Reporter:
                swinbank John Swinbank
                Watchers:
                Frossie Economou, John Swinbank, Joshua Hoblitt, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel