action #111743
Updated by JERiveraMoya almost 2 years ago
#### Motivation See #109187 It is done for SLE-15-SP{3,4} SLE-15-SP3 in #109214. Let's try to reuse the same AutoYaST profile for the rest of the products in maintenance. Previous experience indicated that any minimal failure/mistake setting this basically cascade to all job group, for that reason it is better to do in Development job group. Then we will file another ticket to deploy this in YaST MU job group. #### Scope Test suites with external dependencies: mru-install-desktop-with-addons & mru-install-minimal-with-addons Products: rest of the products in maintenance. #### Acceptance criteria **AC1**: New AutoYaST test suites are created in 'YaST YaST Maintenance Updates - Development' openQA job group corresponding to mru-install-desktop-with-addons & mru-install-minimal-with-addons. **AC2**: Copies of the chained Chained dependencies of test suites mru-install-desktop-with-addons & mru-install-minimal-with-addons which are in YaST MU job group will be set to new AutoYaST test suites in 'YaST Maintenance Updates - Development' job group suites. **AC3**: If we cannot reuse the AutoYaST profile created for SLE-15-SP{3,4} SLE-15-SP3 consider to reduce the scope of products to migrate to AutoYaST. the products. #### Suggestions * Reuse knowledge from previous task: #107674 #109187 * We could reuse very likely the AutoYaST profiles created for SLE-15-SP3. * We should rename all test suite creating AutoYaST image to `autoyast_create_*` so we can distinguish better between old and new things regardless of the job group, maintenance or product as it might be confusing.