"description":"Maintainer: okurz\n\nInstall base+minimal unregistered but enable the system and add SDK after installation using proxy-SCC. Can be used as an image generation job for downstream scenarios when modules should not / can not be added during installation. See https://progress.opensuse.org/issues/19862 for details."
"description":"Maintainer: asmorodskyi,okurz image creation job used as parent for other jobs testing based on existing installation. Installation in textmode and selecting the textmode \"desktop\" during installation. ppc6le needs a bigger disk space because of different sector size."
"description":"Maintainer: okurz, rpalethorpe\n\nIn the current state (as of 2017-01) SLE as well as openSUSE can detect an existing cryptlvm installation and offer to activate it. However, as might be unexpected, the proposed partition layout does not propose an encrypted layout based on this. Only if the cryptlvm layout is selected explicitly it will be encrypted again. This test was added as there was a bug preventing even the recomputation.",
"description":"Maintainer: okurz, jpupava\n\nDuring SLE 12 SP2 development yast gained the feature to update itself from an online repository during installation. During RC-phase this feature was disabled by default. Here we test the feature by explicitly enabling it. No hard checks are done that the self-updating really happens. The scenario only checks that installation can succeed."
},
{
"settings":[
{
"key":"ASSET_1",
"value":"autoinst.xml"
},
{
"key":"AUTOYAST",
"value":"ASSET_1"
},
{
"value":"22",
"key":"HDDSIZEGB"
},
{
"value":"1",
"key":"INSTALLONLY"
},
{
"value":"clone_system",
"key":"START_AFTER_TEST"
}
],
"description":"Parent job produces autoyast profile after successful completion. This test uses generated profile to do autoyast installation.",
"name":"autoyast_reinstall"
},
{
"name":"autoyast_reinstall_ppc",
"settings":[
{
"value":"autoinst.xml",
"key":"ASSET_1"
},
{
"value":"ASSET_1",
"key":"AUTOYAST"
},
{
"value":"30",
"key":"HDDSIZEGB"
},
{
"key":"INSTALLONLY",
"value":"1"
},
{
"key":"START_AFTER_TEST",
"value":"clone_system"
}
],
"description":"Parent job produces autoyast profile after successful completion. This test uses generated profile to do autoyast installation.\nSeparate test for ppc is needed because of different disk size, which has to match parent job."
"description":"Maintainer: zluo\n\nTest for yast2 UI (including ncurses and gnome). Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests."
},
{
"settings":[
{
"value":"textmode",
"key":"DESKTOP"
},
{
"key":"PATTERNS",
"value":"base,minimal"
},
{
"key":"SCC_REGISTER",
"value":"installation"
}
],
"description":"textmode installation with base and minimal pattern registered via proxy SCC",
"name":"minimal+base+proxy_SCC"
},
{
"name":"textmode+xen_server_role",
"description":"Selects Xen role in System Role window (12SP2+).",
"description":"https://progress.opensuse.org/issues/9900\nthis is only the working part, there are few bugs",
"name":"nis_server"
},
{
"name":"smb+xfs",
"description":"Maintainer: mgriessmeier@suse.com, thehejik@suse.com, okurz@suse.com\n\nTest installation via samba server on o.s.d.\nConfigured smb+xfs in combination as xfs just to have some variety and cover xfs a bit more.",
"settings":[
{
"key":"FILESYSTEM",
"value":"xfs"
},
{
"key":"INSTALLONLY",
"value":"1"
},
{
"key":"INSTALL_SOURCE",
"value":"smb"
},
{
"value":"1",
"key":"NETBOOT"
}
]
},
{
"name":"gnome_smb",
"settings":[
{
"value":"gnome",
"key":"DESKTOP"
},
{
"value":"1",
"key":"INSTALLONLY"
},
{
"key":"INSTALL_SOURCE",
"value":"smb"
}
],
"description":"Install gnome using smb and MIRROR_SMB variable available in Leanos-DVD flavor (only)"
},
{
"description":"Maintainer: okurz, jpupava\n\nAlso see test_suite *yast_self_update*.\nWith SLE 12 SP3 build 0271 self-update of installer was enabled (again) by default. This test now tests explicit disabling. No hard checks are done that the self-updating is really disabled. The scenario only checks that installation can succeed.",
"settings":[
{
"key":"INSTALLER_NO_SELF_UPDATE",
"value":"1"
},
{
"key":"INSTALLONLY",
"value":"1"
}
],
"name":"yast_no_self_update"
},
{
"description":"Maintainer: asmorodskyi, okurz. Extratests which were designed to run on gnome",
"description":"Maintainer: asmorodskyi, okurz \nExtratests which were designed to run in console\nx86 and ppc are using different block size so snapper_cleanup test needs bigger hdd."
},
{
"name":"RAID0",
"settings":[
{
"key":"INSTALLONLY",
"value":"1"
},
{
"value":"0",
"key":"RAIDLEVEL"
}
],
"description":"Installation of RAID0 using expert partitioner"
},
{
"name":"USBinstall",
"description":"Install from USB medium, e.g. virtual USB thumbdrive",
"settings":[
{
"value":"1",
"key":"USBBOOT"
}
]
},
{
"name":"multipath",
"settings":[
{
"value":"gnome",
"key":"DESKTOP"
},
{
"key":"INSTALLONLY",
"value":"1"
},
{
"key":"MULTIPATH",
"value":"1"
}
],
"description":"Test installation on machine with virtual multipath hardware. Only tests succesful detection of multipath and installation. No functional testing of multipath itself."
"description":"Snapper + BTRFS related tests\nMaintainer: yxu",
"name":"extra_test_filesystem"
},
{
"description":"Maintainer: jpupava Packages are installed by default and removed when starting with - (minus). Installation get blocked by removed grub2 package,\npackages in INSTALLATION_BLOCKED will be selected back to resolve conflict and continue with installation\nhttps://progress.opensuse.org/issues/9476",
"description":"image creation job used as parent for other jobs testing based on existing installation. To be used as `START_AFTER_TEST=create_hdd_gnome`",
"description":"Maintainer: okurz@suse.de\nClone the system into an autoyast profile to be used by downstream jobs, e.g. to test reinstall from that profile."
"description":"Maintainer: rbrown@suse.de; Basic installation test to confirm that installing and booting to an nvme as your root disk works",
"name":"nvme"
},
{
"description":"jpupava: Also test invalid SCC URL https://trello.com/c/N09TRZxX/968-3-don-t-crash-on-invalid-regurl-on-linuxrc-commandline",
"settings":[
{
"key":"DESKTOP",
"value":"textmode"
},
{
"value":"1",
"key":"IMPORT_UNTRUSTED_KEY"
},
{
"key":"SCC_REGISTER",
"value":"installation"
},
{
"value":"http://Server%%.com",
"key":"SCC_URL"
},
{
"key":"SCC_URL_VALID",
"value":"http://Server-%BUILD%.proxy.scc.suse.de"
},
{
"key":"VIDEOMODE",
"value":"text"
}
],
"name":"textmode+proxy_SCC"
},
{
"name":"autoyast_sle12_btrfs",
"settings":[
{
"key":"AUTOYAST",
"value":"autoyast/autoyast_btrfs.xml"
},
{
"value":"gnome",
"key":"DESKTOP"
},
{
"value":"btrfs",
"key":"FILESYSTEM"
}
],
"description":"Non-default btrfs subvolume structure test for autoyast installation. Verify btrfs in new installation and generation of autoinst.xml. Maintainer: riafarov@suse.com"
"description":"Maintainer: okurz@suse.de, slindomansilla@suse.com\n\nautoyast-supportserver runs in parallel to many jobs, e.g. autoyast installation tests. MAX_JOB_TIME increased to 4h as it was previously failing as incomplete in case of 2h timeout.\n\nAYTESTS_REPO should point to the newest available subproject/repo of the IBS project Devel:YaST"
},
{
"name":"gnome+proxy_SCC+allmodules",
"settings":[
{
"value":"gnome",
"key":"DESKTOP"
},
{
"key":"PATTERNS",
"value":"default,asmm,pcm"
},
{
"key":"SCC_ADDONS",
"value":"phub,asmm,contm,lgm,pcm,tcm,wsm"
},
{
"key":"SCC_REGISTER",
"value":"installation"
}
],
"description":"Maintainers: okurz, dgutu\nInstall all module which are available through ProxySCC\nInstall as patterns during installation."
},
{
"name":"extra_test_filesystem_ppc",
"description":"Snapper + BTRFS related tests for ppc Maintainer: yxu",
"description":"Maintainer: okurz@suse.de, rbrown@suse.de\n\nInstallation with SDK plus all patterns selected for installation to check for potential package conflicts, how the system handles big space usage, etc.\n\nMAX_JOB_TIMEOUT increased to cover log collection in post_fail_hooks. It should not take that long during successful runs.",
"name":"sdk+allpatterns"
},
{
"name":"gnome+proxy_SCC+allmodules_aarch64",
"settings":[
{
"value":"gnome",
"key":"DESKTOP"
},
{
"value":"pcm,tcm",
"key":"SCC_ADDONS"
},
{
"key":"SCC_REGISTER",
"value":"installation"
}
],
"description":"Maintainers: okurz, dgutu\nInstall modules which are available for aarch64. For now we have only 3."
"description":"Maintainer: asmorodskyi,okurz\n\nimage creation job used as parent for other jobs testing based on existing installation. Installation in textmode and selecting the textmode \"desktop\" during installation. Explicitly selecting a bigger disk size as the test relies on snapshots being present which is only the case when the HDD is big enough."
"description":"Same as sles12_qa_acceptance_process_stress. Could not reuse original because need to define START_AFTER_TEST parameter to s390x specific rest suite. See poo#18936.",
"description":"Same as sles12_qa_acceptance_fs_stress. Could not reuse original because need to define START_AFTER_TEST parameter to s390x specific rest suite. See poo#18936.",
"description":"Same as create_hdd_minimal_base+sdk. Could not reuse original one because if we add sdk iso it may not be there. For s390x and zVM we don't have dvd drive, so even if ISOs are defined, they are never used. However, if ISO file is not there, which may happen for this architecture, test will fail immediately. See poo#18936.\nNOTE: ADDONURL_SDK changed, original value:\nADDONURL_SDK=ftp://openqa.suse.de/SLE-%VERSION%-SDK-POOL-%ARCH%-Build%BUILD_SDK%-Media1/\n",
"description":"riafarov: I removed settings for support server, as not needed here. Backup:\nNICTYPE=tap\nPARALLEL_WITH=autoyast-supportserver\nPXEBOOT=1\nWORKER_CLASS=tap",
"description":"Same as sles12_qa_acceptance_sched_stress. Could not reuse original because need to define START_AFTER_TEST parameter to s390x specific rest suite. See poo#18936.",