QA

Some thoughts on this:

• Accessible could mean simply via gitlab? So maybe the GitLab Pages mechanism might be the easiest option
• As results are linked on the public wiki, maybe they should be exposed outside the VPN?
• openqa_suse_de_status.html is written by bin/openqa-review-daily-email via .gitlab-ci.yml

cdywan wrote:

Some thoughts on this:

• Accessible could mean simply via gitlab? So maybe the GitLab Pages mechanism might be the easiest option

Well, I think it can be even easier with just https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html#access-the-latest-job-artifacts-by-url

• As results are linked on the public wiki, maybe they should be exposed outside the VPN?

That's out of scope for the current story.

• openqa_suse_de_status.html is written by bin/openqa-review-daily-email via .gitlab-ci.yml

correct :)

osukup wrote:

i'll try

Do you have a branch? Iirc you mentioned it on Rocket.Chat but no update here yet

osukup wrote:

@okurz for render as html artifact needs enabled Gitlab Pages in project. And it should automatically render saved artifact

True. But AFAICS in https://gitlab.suse.de/openqa/openqa-review/pages there is nothing to "enable" but one would need to add a domain. I don't know if gitlab pages is enabled for the instance gitlab.suse.de and if yes, what domain we can or should use. Also, as you are a member of the parent project scope https://gitlab.suse.de/openqa/ can you access https://gitlab.suse.de/openqa/openqa-review/pages ? should I need to add you as owner/maintainer in the project itself to check?

If the plain html output files are not rendered as such directly from artifact URLs and if gitlab pages does not work for us then maybe we should scp the files to a host that can provide a web server, e.g. w3.nue.suse.com

okurz wrote:

osukup wrote:

@okurz for render as html artifact needs enabled Gitlab Pages in project. And it should automatically render saved artifact

True. But AFAICS in https://gitlab.suse.de/openqa/openqa-review/pages there is nothing to "enable" but one would need to add a domain. I don't know if gitlab pages is enabled for the instance gitlab.suse.de and if yes, what domain we can or should use. Also, as you are a member of the parent project scope https://gitlab.suse.de/openqa/ can you access https://gitlab.suse.de/openqa/openqa-review/pages ? should I need to add you as owner/maintainer in the project itself to check?

unfortuanetly I'm only developer ... so I can't set this and I dont see pages

Yes , in settings>pages it needs add domain and then it shows what to set for dns records needed for gitlab pages

If the plain html output files are not rendered as such directly from artifact URLs and if gitlab pages does not work for us then maybe we should scp the files to a host that can provide a web server, e.g. w3.nue.suse.com

I bumped your permissions in https://gitlab.suse.de/groups/openqa/-/group_members so feel free to experiment with gitlab pages and a domain for openqa-review.

You also referenced https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/1780 for DNS entries.

openqa-review has an entry for http://openqa-review.suse.de/ which so far yields error 301 with no content behind. Maybe we need for the next CI job to publish something. The jobs already store the html document as artifact, e.g. https://gitlab.suse.de/openqa/openqa-review/-/jobs/428496/artifacts/file/openqa_suse_de_status.html

For proper display we also need https://github.com/os-autoinst/openqa_review/tree/master/dashboard_files published on the "gitlab pages"

--> looks like Gitlab Pages aren't working in our instance correctly --> http://openqa-review.suse.de redirects in all cases to localhost :(

--> plan ask infra + @jbaier_cz what with this

or use plan b) SCP artifact outside gitlab to publish on different server

osukup wrote:

--> looks like Gitlab Pages aren't working in our instance correctly --> http://openqa-review.suse.de redirects in all cases to localhost :(

--> plan ask infra + @jbaier_cz what with this

Brief reminder on the recommended workflow:

For EngInfra tickets first create tracker ticket in https://progress.opensuse.org/projects/openqa-infrastructure/issues/ , then create EngInfra ticket with "[openqa] …" in subject, optional "[openqa][urgent] …", reference progress ticket, CC osd-admins@suse.de . Use the tracker ticket for internal notes

ticket to infra -> https://infra.nue.suse.com/Ticket/Display.html?id=189390

for now this link works: https://openqa.io.suse.de/openqa-review/openqa_suse_de_status.html

osukup wrote:

for now this link works: https://openqa.io.suse.de/openqa-review/openqa_suse_de_status.html

I get ERR_TOO_MANY_REDIRECTS there

cdywan wrote:

osukup wrote:

for now this link works: https://openqa.io.suse.de/openqa-review/openqa_suse_de_status.html

I get ERR_TOO_MANY_REDIRECTS there

hmm, something new, few days ago it worked. And @tinita updated ticket

this looks awesome and it also seems have proper https. So what is actually that you want to have on top? If there is nothing important left just call it done because the acceptance criterion is fulfilled? We want to continue with gitlab pages in further work in the epic anyway, e.g. to reference individual reports.

okurz wrote:

this looks awesome and it also seems have proper https. So what is actually that you want to have on top?

own custom domain, as you see it uses https://GROUP.io.suse.de/REPO/ --> we have in dns prepared https://openqa-review.suse.de

modified to publish only osd run

are you also getting reminders? Do we need to escalate https://infra.nue.suse.com/SelfService/Display.html?id=189390 since there was no reaction since 21 days?

please split the "use another custom domain" part into a separate ticket to wait for the SUSE-IT SD ticket. I consider the original ACs done and would for now go with what we have, i.e. https://openqa.io.suse.de/openqa-review/

Same as for parent ticket moving to "QA" project as I would like to simplify access to others even though this is a "SUSE-internal task".

eng infra for custom domain tracking https://jira.suse.com/browse/ENGINFRA-724