https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842016-11-21T16:03:29ZopenSUSE Project Management ToolopenQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=323822016-11-21T16:03:29Zcoolocoolo@suse.com
<ul></ul><ul>
<li>1. is unfeasible - too many jobs have a bug reference thanks to carry over. And unfortunately having a bug reference or not does not relate to the test linked somewhere</li>
<li>2a. you will need to specify what not to remove</li>
<li>2b. link to what latest? The only information left from a removed job is that it's not there</li>
</ul>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=327342016-11-25T16:53:36Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/32734/diff?detail_id=33452">diff</a>)</li><li><strong>Category</strong> changed from <i>Regressions/Crashes</i> to <i>Feature requests</i></li></ul><p>We discussed in a call some ideas:</p>
<ul>
<li>use labels, e.g. <code>label:linked</code> for every job that was linked in a bug report and keep these jobs around longer as "important" ones, same as all jobs that belong to "important" builds. </li>
<li>use automatic script based on apache logs or maybe from within openQA when a job page is called and it has a bug reference which has not been added by automatic means, consider this job as "important" by putting the automatic label in the comment.</li>
</ul>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=328402016-11-28T09:49:51Zoholecekoholecek@suse.com
<ul><li><strong>Assignee</strong> set to <i>oholecek</i></li></ul><p>I'll into this. I'm for tracking referral header instead of apache log parsing. How about adding <code>label:linked</code> for all jobs with referral header present? I still need to look into how apache proxy handles them though.</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=330422016-11-29T12:17:00Zoholecekoholecek@suse.com
<ul></ul><p>I have one issue with this though and that updating job label if referer is present violates REST rules. Get request should not modify data.</p>
<p>What are your opinions on this?</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=330442016-11-29T12:24:21Zcoolocoolo@suse.com
<ul></ul><p>As long as you don't use the credentionals of the one GETing, I see no difference to the approach with parsing logs</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=330522016-11-29T13:29:36Zoholecekoholecek@suse.com
<ul></ul><p>As I am updating comment user queries, I'm wondering do we have something against creating system user?</p>
<p>Currently I'm taking same approach as in case of audit log where event owner db field is nullable and there are explicit checks for valid user. Comments does not have nullable user yet -> schema migration. And there are at least 5 occurrences of $user->... which needs explicit user checking.</p>
<p>Whereas if I check and create system user on webui startup I can use its id for comments instead of undef. Thus no need for migration and unnecessary code changes. This system user wont have proper openid URL thus there is no conflict with existing users. Also I can use fixed string for gravatar -> all openqa instances should have the same picture for admin user from gravatar.</p>
<p>I'm inclined to add this user. WDYT?</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=337782016-12-06T16:06:29Zoholecekoholecek@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>PR with job labeling and expiration merged <a href="https://github.com/os-autoinst/openQA/pull/1060" class="external">PR#1060</a>. What is missing is the flagging of label carry-over and considering all labeled jobs important</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=338182016-12-07T12:51:06Zokurzokurz@suse.com
<ul></ul><p>And some documentation should be added, at least on <a href="https://progress.opensuse.org/projects/openqav3/wiki" class="external">https://progress.opensuse.org/projects/openqav3/wiki</a> if not directly within the documentation of openQA</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=338622016-12-07T20:38:01Zokurzokurz@suse.com
<ul></ul><p><a href="https://github.com/os-autoinst/openQA/pull/1071" class="external">https://github.com/os-autoinst/openQA/pull/1071</a> changes the behaviour for labels. They are not carried over anymore. Please think hard if this is what we want.</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=339362016-12-08T21:20:03Zokurzokurz@suse.com
<ul></ul><p><a href="https://github.com/os-autoinst/openQA/pull/1071" class="external">https://github.com/os-autoinst/openQA/pull/1071</a> merged, what do we need to do now?</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=339562016-12-09T09:05:32Zcoolocoolo@suse.com
<ul></ul><p>updating the documentation I'd say</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=339882016-12-09T12:06:29Zokurzokurz@suse.com
<ul></ul><p>we agreed in the call that <a class="user active user-mention" href="https://progress.opensuse.org/users/23010">@szarate</a> will provide his enhancements to the documentation until start of next week. Next step is then to add some admin document also explaining what is happening here.</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=340002016-12-09T13:53:14Zszarate
<ul></ul><p>In the meantime, so this doesn't gets blocked, it can be a separate document. Until a proper adminguide is written (Or simply add this as part of it, as the first topic, then we could move stuff like Installing.asciidoc#other-database-engines there (If it makes sense also)</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=340022016-12-09T14:27:05Zokurzokurz@suse.com
<ul></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/23010">@szarate</a> don't try to get out of there. I deliberately mentioned that we are <em>blocked</em> by you to give some additional motivation ;-P</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=340702016-12-12T13:01:01Zszarate
<ul></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/17668">@okurz</a> good one!, Will give some love to that then :) </p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=344982016-12-19T07:13:53Zcoolocoolo@suse.com
<ul><li><strong>Subject</strong> changed from <i>job data is cleaned up way too eagerly, e.g. for still open bugs</i> to <i>(missing docu) job data is cleaned up way too eagerly, e.g. for still open bugs</i></li><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>Normal</i></li></ul><p>As the feature itself is done and merged, I move down the priority</p>
openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=364462017-01-17T16:55:27Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> set to <i>Milestone 5</i></li></ul> openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=366982017-01-18T16:23:11Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-6 priority-3 priority-lowest closed" href="/issues/12266">action #12266</a>: keep tests with any comment around later</i> added</li></ul> openQA Project - action #14926: (missing docu) job data is cleaned up way too eagerly, e.g. for still open bugshttps://progress.opensuse.org/issues/14926?journal_id=376662017-01-30T12:59:03Zoholecekoholecek@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>Documentation added in <a href="https://github.com/os-autoinst/openQA/pull/1206" class="external">https://github.com/os-autoinst/openQA/pull/1206</a></p>