https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-12-16T10:38:57ZopenSUSE Project Management ToolQA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=3585282020-12-16T10:38:57Zokurzokurz@suse.com
<ul><li><strong>Tracker</strong> changed from <i>coordination</i> to <i>action</i></li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=3585302020-12-16T10:39:10Zokurzokurz@suse.com
<ul><li><strong>Project</strong> changed from <i>openQA Project</i> to <i>QA</i></li><li><strong>Category</strong> deleted (<del><i>Feature requests</i></del>)</li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=3585582020-12-16T11:19:13Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-1 priority-3 priority-lowest" href="/issues/77317">action #77317</a>: chat bot to conduct daily checks, alerts, reminders, etc.</i> added</li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=3979712021-04-15T20:00:14Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4042452021-05-05T18:39:04Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Ready</i> to <i>future</i></li></ul><p>this was an idea by the team and for the team but apparently there is not much interest so I will move it out of the backlog for now</p>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4314622021-07-29T11:06:22Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>test out rocket chat notifications from github actions</i> to <i>test out chat service notifications, e.g. rocket chat, from github actions</i></li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4390012021-08-27T08:01:27Zlivdywanliv.dywan@suse.com
<ul><li><strong>Subject</strong> changed from <i>test out chat service notifications, e.g. rocket chat, from github actions</i> to <i>test out chat service notifications, e.g. slack, from github actions</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/439001/diff?detail_id=416252">diff</a>)</li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4393882021-08-30T08:25:08Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>test out chat service notifications, e.g. slack, from github actions</i> to <i>test out chat service notifications, e.g. matrix, from github actions</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/439388/diff?detail_id=416618">diff</a>)</li><li><strong>Target version</strong> changed from <i>future</i> to <i>Ready</i></li></ul><p>I am not really motivated to support proprietary tools before free software so I suggest to use matrix/element first</p>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4397302021-08-31T08:36:45ZVANASTASIADISvasilios.anastasiadis@suse.com
<ul><li><strong>Assignee</strong> set to <i>VANASTASIADIS</i></li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4399822021-08-31T19:10:11ZVANASTASIADISvasilios.anastasiadis@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4402702021-09-01T12:45:21ZVANASTASIADISvasilios.anastasiadis@suse.com
<ul></ul><p>There is a working matrix solution (currently on a personal test repo, but easily reproducible in any workflow with minor additions). I am wondering however:</p>
<ul>
<li>currently in the <code>scripts</code> repo there are 2 jobs, containing 3 steps in the workflow:
JOB 1:
a) check WIP limits
b) set due dates
JOB 2:
c) run ci tests on push</li>
</ul>
<p>I'm wondering: since the first job is a scheduled job, should a notification be sent in <strong>every</strong> failure? That's certainly easier (and less complex), but if for example the job fails on a Friday evening, by monday we'd have a lot of spam in the chat.</p>
<p>Another solution would be saving the previous condition in a file in the repo, and comparing to see if anything changed. That would lead to notifications only the first time something fails. But it would still miss other cases: for example, a case where the same job/step fails but for a different reason.</p>
<p>I think it's simpler in the case of <a href="https://github.com/os-autoinst/qa-tools-backlog-assistant:" class="external">https://github.com/os-autoinst/qa-tools-backlog-assistant:</a> notify only on status change for every query. If "overall" backlog is off limits, you get one notification: the next one will be when it's inside limits again.</p>
<p>Depending on the job in question, different ways of notifying may be prefferable: for some jobs only once on every change, on others only one report in fixed intervals... I would appreciate other opinions and thoughts here.</p>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4416442021-09-02T11:56:10Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>test out chat service notifications, e.g. matrix, from github actions</i> to <i>test out chat service notifications, e.g. matrix, from github actions size:M</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/441644/diff?detail_id=418664">diff</a>)</li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4429892021-09-07T08:22:54Zlivdywanliv.dywan@suse.com
<ul></ul><p>VANASTASIADIS wrote:</p>
<blockquote>
<p>There is a working matrix solution (currently on a personal test repo, but easily reproducible in any workflow with minor additions). I am wondering however:</p>
</blockquote>
<p>What solution is that? Do you have a proof of concept implementing this?</p>
<blockquote>
<ul>
<li>currently in the <code>scripts</code> repo there are 2 jobs, containing 3 steps in the workflow:
JOB 1:
a) check WIP limits
b) set due dates
JOB 2:
c) run ci tests on push</li>
</ul>
<p>I'm wondering: since the first job is a scheduled job, should a notification be sent in <strong>every</strong> failure? That's certainly easier (and less complex), but if for example the job fails on a Friday evening, by monday we'd have a lot of spam in the chat.</p>
</blockquote>
<p>What do you consider "a lot"? I would suggest to aim for one notification a day. I don't care if we see the exact same the day after, that just means we need to catch up.</p>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4470452021-09-17T08:55:04ZVANASTASIADISvasilios.anastasiadis@suse.com
<ul></ul><p>pr: <a href="https://github.com/os-autoinst/scripts/pull/108" class="external">https://github.com/os-autoinst/scripts/pull/108</a></p>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4490222021-09-24T09:19:37ZVANASTASIADISvasilios.anastasiadis@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4526852021-10-06T09:30:52Zlivdywanliv.dywan@suse.com
<ul></ul><p>We still need these items here:</p>
<ul>
<li>We need #suse-qe-tools to receive notifications</li>
<li>Add secrets to the GitHub pipeline</li>
<li>We need a bot account for Matrix</li>
</ul>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4626262021-11-10T10:50:07Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" href="/issues/102059">action #102059</a>: Integrate the Slack feed notifications feature for progress queries</i> added</li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4649332021-11-16T10:20:56Zokurzokurz@suse.com
<ul></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/33800">@VANASTASIADIS</a> what are your own plans on this? Should we unassign you and pick it up within SUSE QE Tools?</p>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4696742021-12-01T10:44:24ZVANASTASIADISvasilios.anastasiadis@suse.com
<ul><li><strong>Assignee</strong> deleted (<del><i>VANASTASIADIS</i></del>)</li></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/17668">@okurz</a> So, for matrix this should be working, as long as someone adds <code>MATRIX_ACCESS_TOKEN</code> and <code>MATRIX_ROOM_ID</code> to the secrets. I don't have the permissions to add secrets, so someone with the appropriate permissions should do that.</p>
<p>In addition, I see that this has rolled back to being slack-centric. So I will unassign and feel free to assign and add the secrets, or proceed with a slack implementation. If it's not too urgent and you have no free hands, I can tackle the slack implementation too, after I'm done with a couple of qe-core tickets. Ping me in that case.</p>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4745342021-12-19T20:11:06Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>New</i></li></ul><p>Actually hasn't rolled back to being "slack-centric". For Slack I was merely using quite a different feature in the related but not same ticket <a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" title="action: Integrate the Slack feed notifications feature for progress queries (Resolved)" href="https://progress.opensuse.org/issues/102059">#102059</a></p>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4773602022-01-04T14:44:38Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4827462022-01-21T13:30:21Zmkittlermarius.kittler@suse.com
<ul></ul><p>It is still not clear to me whether this should now be implemented for Matrix or for Slack.</p>
<p>Considering <a href="https://github.com/os-autoinst/scripts/pull/108" class="external">https://github.com/os-autoinst/scripts/pull/108</a> it seems the Matrix part might have already been concluded and only Slack is left. Even if that's the case I'm still wondering where the Matrix messages end up as the room name it literally a <a href="https://github.com/os-autoinst/scripts/settings/secrets/actions" class="external">secret</a> (and one can only update/remove them).</p>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=4836172022-01-25T12:34:07Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Ready</i> to <i>future</i></li></ul><p>mkittler wrote:</p>
<blockquote>
<p>It is still not clear to me whether this should now be implemented for Matrix or for Slack.</p>
<p>Considering <a href="https://github.com/os-autoinst/scripts/pull/108" class="external">https://github.com/os-autoinst/scripts/pull/108</a> it seems the Matrix part might have already been concluded and only Slack is left. Even if that's the case I'm still wondering where the Matrix messages end up as the room name it literally a <a href="https://github.com/os-autoinst/scripts/settings/secrets/actions" class="external">secret</a> (and one can only update/remove them).</p>
</blockquote>
<p>Yes, the matrix part is only done when we actually see messages, not in before :) The priority should be 1. Matrix, then 2. Slack. But as this apparently wasn't interesting for the team to pick up for some time I will for now remove the ticket from our backlog again until someone or something convinces me again :)</p>
QA - action #81106: test out chat service notifications, e.g. matrix, from github actions size:Mhttps://progress.opensuse.org/issues/81106?journal_id=6018682023-02-14T16:02:08Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>Rejected</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>okurz wrote:</p>
<blockquote>
<p>I am not really motivated to support proprietary tools before free software so I suggest to use matrix/element first</p>
</blockquote>
<p>I give up ¯(°_o)/¯ <a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" title="action: Integrate the Slack feed notifications feature for progress queries (Resolved)" href="https://progress.opensuse.org/issues/102059">#102059</a> must suffice for now</p>