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

ap_verify fails in the official release pipeline due to version mismatch

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: jenkins
    • Labels:
      None
    • Team:
      Architecture
    • Urgent?:
      No

      Description

      The ap_verify pipeline runs the code from a release container against a series of datasets specified in the etc/scipipe/ap_verify.yaml configuration file. That file specifies the git ref to be checked out for each dataset. For normal nightly builds and even weeklies, it is OK to test against the main branch. (Nightlies have no alternative, as there isn't a nightly git tag.) But when testing an official release container, the version of the dataset to be used may be quite a bit older than main.

      We should add a DATASET_REF job parameter that can override ds.git_ref in the verifyDataset pipeline function in scipipe/ap_verify.groovy and make sure to set that to the gitTag when starting the ap_verify job in release/official_release.groovy.

        Attachments

          Issue Links

            Activity

            Hide
            ktl Kian-Tat Lim added a comment -

            Small update +7 -0.

            Show
            ktl Kian-Tat Lim added a comment - Small update +7 -0.
            Hide
            ktl Kian-Tat Lim added a comment -

            Reviewed on PR.

            Show
            ktl Kian-Tat Lim added a comment - Reviewed on PR.

              People

              Assignee:
              ktl Kian-Tat Lim
              Reporter:
              ktl Kian-Tat Lim
              Reviewers:
              Matthias Wittgen
              Watchers:
              Kian-Tat Lim, Matthias Wittgen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.