Details
-
Type:
Story
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: ap_verify
-
Labels:None
-
Team:Architecture
-
Urgent?:No
Description
From Kian-Tat Lim post on dm-ccb channel:
ap_verify test code that executes against a containerized version of the Science Pipelines using data in a git LFS repository, generating algorithmic and computational performance measurements. Normally the ap_verify code itself comes from the same container, although we have the capability in Jenkins to use a branch of ap_verify against the same or a different version of the rest of the Pipelines.
Between the time that the v20.0.0rc1 tag was created (which is also the v20.0.0 tag) and today when we are attempting to run the release procedure, the ap_verify test code and its data (actually a config file in the data repo) were updated.
The release pipeline attempts to use the v20.0.0 container including ap_verify code tagged as v20.0.0 against the master branch of the data.
This ticket seems like a description of what happened, rather than a request for action. Kian-Tat Lim, I think you had a couple of different proposals for how we could prevent this happening in the future — could you fill them in here, please?