https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-10-09T15:54:48ZopenSUSE Project Management ToolopenQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1549312018-10-09T15:54:48Zriafarov
<ul><li><strong>Due date</strong> set to <i>2018-10-23</i></li><li><strong>Start date</strong> changed from <i>2018-08-31</i> to <i>2018-10-09</i></li></ul><p>due to changes in a related task</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1549462018-10-09T15:59:10Zriafarov
<ul><li><strong>Assignee</strong> set to <i>riafarov</i></li></ul> openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1549942018-10-09T21:06:03Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Enhancement to existing tests</i></li><li><strong>Target version</strong> set to <i>Milestone 21</i></li></ul><p>As I understood from the personal discussions we have the plan also only relates to osd and not o3. However, still I have talked to the openSUSE RMs what they think about multiple subgroups -> main question by dimstar was: what is the benefit for RMs when they mainly review and can we find a view to show the results from multiple job groups. I guess what we can think about is slightly changing the behaviour of "parent job groups" on the index page of openQA to provide a link to a test overview page which shows multiple job groups at the same time as referencing multiple job groups in the openQA test overview page already is supported.</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1578412018-10-16T14:55:00Zriafarov
<ul></ul><p>Some feedback regarding changes to o3:<br>
riafarov: the main concerns are around ttm, which does not (yet) cope with it as well as having to check multiple groups to find out why a snapshot can't be published - from that PoV, the split is a 'bad thing(tm)'<br>
riafarov, while I don't object, I would be nervous about the impact this split will have on the broader audience of visitors to openqa.opensuse.org - will the job groups be split and named appropriately that they'll make sense to joe on the street? How will they know which jobgroups are relevant to the release process, and which ones aren't?<br>
riafarov, right now it's relatively easy.. only the openSUSE Tumbleweed job group is relevant to the release of openSUSE Tumbleweed, for example. Kernel, aarch64, power, are not<br>
riafarov, I think it would be a prerequisite for any split that the openqa.opensuse.org webui can make it very apparent which are relevant to the release of which product<br>
riafarov, also from a Kubic perspective, I'd be very , very, very, interested in how you'd split that. It is absolutely imperative, as part of the very existence of the Kubic project, that it's testing is integrated as part of the TW release process. and I do not want to have to check two places for it's status</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1590142018-10-19T13:58:44Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2018-10-23</i> to <i>2018-11-06</i></li></ul><p>due to changes in a related task</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1608382018-10-29T14:16:48Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2018-11-06</i> to <i>2018-11-20</i></li></ul><p>due to changes in a related task</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1697122018-11-28T17:13:00Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-12-04</i> to <i>2018-12-18</i></li></ul><p>due to changes in a related task</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1746742018-12-18T10:44:22Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2018-12-18</i> to <i>2019-01-15</i></li></ul><p>due to changes in a related task</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1751482018-12-19T10:59:31Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 21</i> to <i>Milestone 22</i></li></ul> openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1778452019-01-09T13:53:07Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> changed from <i>2019-01-15</i> to <i>2019-02-12</i></li></ul><p>due to changes in a related task</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1895332019-02-17T18:55:38Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>Blocked</i></li><li><strong>Target version</strong> changed from <i>Milestone 22</i> to <i>Milestone 23</i></li></ul><p>"Blocked" by subtasks?</p>
<p><a class="user active user-mention" href="https://progress.opensuse.org/users/25024">@riafarov</a> do you agree that we should be able to finish this epic within M23?</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1902442019-02-18T14:01:12Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> changed from <i>2019-02-26</i> to <i>2019-03-26</i></li></ul><p>due to changes in a related task</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=1980892019-03-12T10:42:13Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 23</i> to <i>Milestone 25</i></li></ul><p>-> <a class="issue tracker-4 status-3 priority-4 priority-default closed child behind-schedule" title="action: [sle][functional][y] implement validation for encrypt lvm test suites (Resolved)" href="https://progress.opensuse.org/issues/48173">#48173</a></p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=2175742019-06-03T13:53:07Zriafarov
<ul><li><strong>Status</strong> changed from <i>Blocked</i> to <i>Resolved</i></li></ul><p>I believe we have established separate job group. Follow up tasks are visible in the saga, this is ongoing.</p>
openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=3338502020-10-12T13:37:15Zszarate
<ul><li><strong>Tracker</strong> changed from <i>action</i> to <i>coordination</i></li></ul> openQA Tests - coordination #42191: [functional][y][epic] Have separate job group for YaST subteamhttps://progress.opensuse.org/issues/42191?journal_id=3346692020-10-12T13:46:20Zszarate
<ul></ul><p>See for the reason of tracker change: <a href="http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html" class="external">http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html</a></p>