Iss2189 - Remove z/OS inttests from schedule as there are equivalent IVTs #225
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Jade Carino <[email protected]>
eamansour
approved these changes
Apr 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
Part of story galasa-dev/projectmanagement#2189
I have set up a new CronJob on cicsk8s that runs the ZosFileManagerIVT, ZosFileDatasetManagerIVT, ZosVSAMManageIVT and ZosBatchManagerIVT on prod1 daily at 6am, with both the RSE API and z/OS MF implementations.
I have removed the equivalent inttests from the schedule by commenting out their @test annotations, as we are trying to remove as many tests as possible that still require the local Galasa ecosystem install on the Linux VM.
I have removed the *Isolated and *Mvp variations of the tests also even though the IVTs can't test this - I discussed with @techcobweb that the Isolated and MVP tests should really be local Galasa tests, not remote ones on a Galasa service, as the Isolated/MVP zip can only be used locally. Story galasa-dev/projectmanagement#2190 covers making an equivalent for these.