Problem
there currently is no check that, when tagging a release for a new StudyDefinition revision, the app as currently deployed in the app store can actually handle that study bundle.
Solution
we should add a check into the CI pipeline, to ensure that new study bundles can only be deployed if the app can actually handle them.
the CI should fetch the latest tagged release from the app repo, build that, point it at a local study bundle (the one we're about to deploy) and verify that the app gets far enough into the onboarding to indicate that it actually was able to process the study bundle
Additional context
the app's CI pipeline already has a similar setup, in that the app's UI tests will use the study bundle generated by the MHC-StudyDefinitions release the app was built against
Code of Conduct
Problem
there currently is no check that, when tagging a release for a new StudyDefinition revision, the app as currently deployed in the app store can actually handle that study bundle.
Solution
we should add a check into the CI pipeline, to ensure that new study bundles can only be deployed if the app can actually handle them.
the CI should fetch the latest tagged release from the app repo, build that, point it at a local study bundle (the one we're about to deploy) and verify that the app gets far enough into the onboarding to indicate that it actually was able to process the study bundle
Additional context
the app's CI pipeline already has a similar setup, in that the app's UI tests will use the study bundle generated by the MHC-StudyDefinitions release the app was built against
Code of Conduct