Project

General

Profile

Actions
Copy link

action #2424

closed

osc plugin: prototype of a mechanism to notify involved users (without repetition)

Added by ancorgs almost 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
aplanas
Target version:
Staging sprint 08
Start date:
2014-05-05
Due date:
% Done:

0%

Estimated time:
20.00 h

Description

The plugin should be able to notify involved users about failed builds and failed tests. The first approach will be writing a comment in the staging project mentioning all the submitters. The plugin will need to store some information about the already notified events, to prevent it to notify twice about the same test result of buildfail if it's invoked several timed (which will happen).

Related issues 2 (0 open — 2 closed)

Related to Staging project workflow - action #2428: Implement comments for projects in OBS APIClosedancorgs2014-05-05

Actions
Related to openQA Project - action #1301: Communicate to OBS the result of the preintegration testRejected2014-01-27

Actions
Actions
Copy link
 #1

Updated by ancorgs almost 10 years ago

Of course, #2428 needs to be done before being able to finish this task.

Actions
Copy link
 #2

Updated by ancorgs almost 10 years ago

  • Assignee set to aplanas
Actions
Copy link
 #3

Updated by ancorgs almost 10 years ago

This page contains a good example of how the comments could look like (last comment at the time of writing this)

https://build.opensuse.org/project/show/openSUSE:Factory:Staging:A

Actions
Copy link
 #4

Updated by aplanas almost 10 years ago

I see the comments, where is the basic API and rules for the plugin.

Actions
Copy link
 #5

Updated by ancorgs almost 10 years ago

In OBS you have the following routes for creating, reading and deleting comments:

  • get 'comments/request/REQUEST_ID'
  • post 'comments/request/REQUEST_ID'
  • get 'comments/package/PROJECT_NAME/PACKAGE_NAME'
  • post 'comments/package/PROJECT_NAME/PACKAGE_NAME'
  • get 'comments/project/PROJECT_NAME'
  • post 'comments/project/PROJECT_NAME'
  • delete 'comment/COMMENT_ID'
Actions
Copy link
 #6

Updated by ancorgs almost 10 years ago

About the rules, the initial proposal (that probably needs refining but is a valid starting point) is in section 4.1 of
http://etherpad.cloud.suse.de/p/obs_and_openqa

Actions
Copy link
 #7

Updated by coolo almost 10 years ago

  • Priority changed from Normal to Urgent
  • Target version deleted (Staging sprint 5)
Actions
Copy link
 #8

Updated by aplanas almost 10 years ago

  • Priority changed from Urgent to Immediate
Actions
Copy link
 #9

Updated by aplanas almost 10 years ago

  • Target version set to Staging sprint 08
Actions
Copy link
 #10

Updated by aplanas almost 10 years ago

[Only to not forget this thought.]

Makes sense to add this methods in https://build.opensuse.org/apidocs?

Actions
Copy link
 #11

Updated by aplanas almost 10 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #12

Updated by aplanas almost 10 years ago

I tried to test the best way I can, but is not enough. For example, I didn't receive any notification from OBS for any comment with @aplanas text.

Also I commented the remove of the comments in the acceptance command to avoid lost of data until there are more test in the code.

Actions
Copy link
 #13

Updated by aplanas almost 10 years ago

  • Status changed from In Progress to Resolved

I will work fixing / adjusting comments when the need appears.

Actions
Copy link

Also available in: Atom PDF