Change VERSION for migration group specific flavor #7624
Merged
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.
For 12sp5 project, we introduce new migration automation scenario 12sp5->15sp1, so some specific change will happen.
We create new flavor Migration-from-SLE12-SP5-to-SLE15-SPx for this kind of test cases, and triggered by VERSION=12-SP5 FlAVOR=Migration-from-SLE12-SP5-to-SLE15-SPx together with other 12sp5 migration test group. And we will have 12sp5 group view on openqa UI once NB is trigger
BUT we need change VERSION to 15-SP1 since only this can let migration code handle correctly to upgrade to 15SP1 in stead of 12-SP5.
This flavor will only using by migration group and will not impact any other group, once 12sp5 project finish, we can delete this special setting.
Welcome any comments.