github: test record ansible results to an ara server

[dmsimard]

If this works, it would provide a better UX than trying to dig through
the ansible console output in the github action.

[dmsimard]

I've set an ARA_API_USERNAME and ARA_API_PASSWORD secret, let's find out if it works.

[dmsimard]

Hmm, I couldn't understand why it didn't work so I went ahead and tried to reproduce it in a test repository I created for this purpose: dmsimard/test-gh-ara#1 and it worked: https://demo.recordsansible.org/playbooks/3188.html

I guess the secret isn't made available to the job until after the patch merges because it's a PR from a fork ?

Putting this in draft for now, we should send it elsewhere than on a demo server :)

Edit: if this worked, we'd have something like https://demo.recordsansible.org/playbooks/3184.html instead of this: https://github.com/ansible-community/antsibull/runs/4245109745?check_suite_focus=true#step:5:1 (in addition to recording results from every job and making them searchable)

[samccann]

hey @dmsimard - is this PR something you are still considering, or should we close it out?

Thanks!

[dmsimard]

It's not something I am actively working on but I've talked to @anweshadas about it a while back.

The idea would be to have an ara server somewhere to send CI/CD results to in this manner for helpful reporting, auditing, troubleshooting, etc. -- better than thousands of lines of stdout in an azure pipeline, anyway, but I am biased :)

In this particular proof of concept I used ara's demo server but it's not meant for production use and costs me money.

If someone would like to set up a server somewhere I can help.

[dmsimard]

To be clear, I meant to demonstrate that logging jobs in ara was just to include an installation of ara and set up some environment variables so it could be widely used if there is interest.

[samccann]

ok cool. I was just doing a bit of tidying up in GH land so will leave this open for now.