QA (public) » openQA Project (public)

If I understood the error correctly, our scripting expects _servicedata to parse changesrevision, so I updated the service to use obs_scm service and generate changelog. Now I am waiting for next run to see the results.

For the alerting, one option could be to use the Atom feed with failures which Jenkins provides: http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/rssFailed

jbaier_cz wrote:

For the alerting, one option could be to use the Atom feed with failures which Jenkins provides: http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/rssFailed

Multiple options exist but I would go with choosing a solution that does not need a specific action by every team member. I just don't know which mailing list would be good. o3-admins doesn't sound like a good match as it's not about o3 nor admins. We could also send to the Slack room email address. No, I think a new mailing list for that purpose would be better as this way anyone interested in the topic "openQA package submission" could subscribe. WDYT?

For now, I created a rule to send failures to our ordinary osd-admins mailing list. I agree that this more related to packaging / OBS stuff. I can live with this solution and I am also OK with a new mailing list related to this kind of notification (for me it would end in the same folder anyway). The main question here is probably if anyone outside our team would be interested to receive error notifications about failed submissions.

The main question here is probably if anyone outside our team would be interested to receive error notifications about failed submissions.

I'd prefer if it just works. If there are likely longer updates, having it posted in slack channel would work for me (maybe into #eng-testing). Other option would be to add it to the developer option on the status web page https://status.opensuse.org/, there is already openQA.

pvorel wrote:

The main question here is probably if anyone outside our team would be interested to receive error notifications about failed submissions.

I'd prefer if it just works. If there are likely longer updates, having it posted in slack channel would work for me (maybe into #eng-testing). Other option would be to add it to the developer option on the status web page https://status.opensuse.org/, there is already openQA.

status.opensuse.org does not fit though as jenkins.qa.suse.de is not a public facing service. The question is only about that. For now we will use osd-admins@suse.de

So it turned out, our scripts cannot (yet) handle containers very well. We are expecting the package to have a spec file which is not the case for containers. I will update to script to handle that situation.