QA

By now I would consider building a custom container and using that in gitlab CI a viable alternative, e.g. as in https://gitlab.suse.de/openqa/auto-review/

Building container in https://build.suse.de/package/show/home:okurz:container/openqa-review with all dependencies and trying out in https://gitlab.suse.de/okurz/openqa-review . Created https://gitlab.suse.de/openqa/openqa-review already.

I would need to put variables like a redmine API key and bugzilla username and password into gitlab config and I would like to avoid my personal user password. hmuelle gave me a bugzilla bot account "QASLE" but first the name is too specific and the email is qa-sle-mgmt. I doubt that ML is a good target. I should ask if we can have a better account created.

EDIT: 2019-11-19: Asked in https://chat.suse.de/channel/suse-it-ama?msg=pXMoXFKaEnk5AfWGw "hi, I would like to have a non-personal bugzilla account backed by a mailing list so that a script from gitlab CI pipeline can post comments which previously I had done with my personal user account but I do not want to save my personal password in gitlab CI variables. Any idea who can help with that?"

Setting to Feedback with reminder due-date to see if I got any response on question in chat.

EDIT: 2019-11-19: fcrozat was kind enough to answer directly, pointed me to RIO ticket. I created a RIO ticket REQ_333370 with content:

hi, I would like to have a non-personal bugzilla account backed by a mailing list so that a script from gitlab CI pipeline can post comments which previously I had done with my personal user account but I do not want to save my personal password in gitlab CI variables.

Preferences:

username: openqa-review
mailing list: openqa-review@suse.de

I already created a ticket for SUSE Engineering Infrastructure to create the mailing list: https://infra.nue.suse.com/SelfService/Display.html?id=154691

EDIT: 2019-11-19: The mailing list was already created: openqa-review@suse.de

no answer in RIO ticket, giving more time.

No response :,( . Asked in https://chat.suse.de/channel/suse-it-ama?msg=7AxwXTow2BijJqLo8 if I can do anything better and added a note in the RIO request.

Pinged again in RC with https://chat.suse.de/channel/suse-it-ama?msg=diXTQaNo35oPWuo49 : "Zuzana van Wijk Vodova hi, you offered your help for REQ_333370 last month and asked me to ping you directly for escalation. Unfortunately there has not been any movement with the request since then. Is there anything I can do myself to move this forward?"

(Finally) received an update in https://rio.microfocuscloud.com/tmtrack/tmtrack.dll?shell=swc&IssuePage&Template=viewwrapper&RecordId=113050&TableId=1003#1 .

C   Chris Slade  -  23/01/2020 10:55:03 PM   -(public)  Send E-mail      
    Note from Chris Slade about REQ_333370 [ttid: 1003,113050]

 Message Address Details
Message Addressed To: Oliver Kurz

Oliver,



There is no such thing as a Bugzilla account. Bugzilla uses the external customer accounts that are created with our self reg service. So you would need to create an external account using that email address. to create a mailing list you will need to contact someone in charge of mailing lists. I believe that Karol Babioch is in charge of the suse.de mailing lists.



Thank you,

Chris Slade

So I created an account "openqa_review" over https://login.microfocus.com , password stored internally in my password manager. I could validate the email address of the mailing list openqa-review@suse.de and proceed now. Over https://bugzilla.suse.com/index.cgi?GoAheadAndLogIn=1 I could not yet validate the account so far unfortunately. Maybe I need to give it some time. Can retry another day.

EDIT: Initialized an account on progress.o.o which also created an API key. I added the API key as well as username and password for bugzilla into https://gitlab.suse.de/openqa/openqa-review/-/settings/ci_cd and started https://gitlab.suse.de/openqa/openqa-review/-/jobs/163830 . I can check for reminder comments on bugzilla with http://fastzilla.suse.de/?q=commenter%3Aopenqa-review%40suse.de . Job was aborted after timeout of 1h, bumped to 4h in gitlab CI config for this project.

https://gitlab.suse.de/openqa/openqa-review/-/jobs/163908 succceeded after 118m.

I added some pipeline schedules on
https://gitlab.suse.de/openqa/openqa-review/pipeline_schedules but after temporary network problems within the network I deactivated the schedules again for now.

Open point: I need to publish the generated report. Previously we just saved to /suse/okurz which isn't available within gitlab CI. We could scp the file out but I prefer to save the report as gitlab CI artifacts assuming I can reference the reports accordingly by URL as documented on https://docs.gitlab.com/ee/user/project/pipelines/job_artifacts.html and at best update the short links to the reports within s.qa's db.

I can try accessing job artifacts with static URLs anytime.

waiting for #75214 first

With #75214 resolved I can look again what is left to be moved from lord.arch to gitlab CI jobs

Moving to "QA" project as I would like to simplify access to others even though this is a "SUSE-internal task".

All openqa-review cron jobs have been replaced by gitlab CI schedules in https://gitlab.suse.de/openqa/openqa-review/-/pipeline_schedules with the results visible in https://openqa.io.suse.de/openqa-review/