#4406 A new bot FAS account for Fedora QA
Closed: Fixed None Opened 9 years ago by kparal.

Hello,

we already have 'autoqa' FAS account. Please create another one for us, named 'fedoraqa'. It should again be marked as "bot". We would also need to disable wiki captcha for it, it that's configured separately. The contact email should be set to fedoraqa-devel-admin@fedoraproject.org .

Thanks!


Does the account need any special groups or just a valid account?

The wiki captcha shouldn't hit authenticated users.

I'll need some way to get you the password, or is this going to be used inside fedora infrastructure?

I assume we don't need any special groups, and we can add the account to own groups (like 'qa') any time ourselves. The account needs to be able to edit wiki pages, which should be possible without any special permissions I think (maybe cla_done?).

The wiki captcha shows for me, even when I'm authenticated. So I'm not exactly sure how it works, but we would need to have it disabled for this bot account, if possible.

This is going to be used from some of our servers which are not yet in fedora infra, AFAIK. Please mail me a GPG-encrypted password, my GPG key kparal@redhat.com has fingerprint 9C237F3A.

Do we want bot status for pseudo-users that have passwords? Especially passwords that are not managed by fedora infra (via the private config management repos)?

A wiki captcha occurs when a link outside of a whitelist of domains is added to a page. I don't believe the wiki has a captcha for authenticated users in otherwise.

Replying to [comment:4 toshio]:

Do we want bot status for pseudo-users that have passwords? Especially passwords that are not managed by fedora infra (via the private config management repos)?

Knowing what kparal has in mind (and since I'm probably going to be tasked with deploying it), I don't think that it has to run outside of infra but it's also not a Fedora package. If we don't run it on infra controlled systems, it'll be part of the qa playbook and the password will be stored in the private git repo on lockbox-comm01.qa.

The initial use case for this bot account is to run a script that takes scheduled test days in fedocal and generates a wiki page listing the upcoming test days so that we can have a single source of test day schedule information.

Could we perhaps enhance fedocal to provide the info you want directly?

A wiki captcha occurs when a link outside of a whitelist of domains is added to a page. I don't believe the wiki has a captcha for authenticated users in otherwise.

Yes, we're going to put hyperlinks to the wiki page. Anything that is in the test day descriptions (links to project pages, etc) will get included in the generated wiki page.

Could we perhaps enhance fedocal to provide the info you want directly?

The use case might be a bit too specific for our needs. We need to parse all our events, find "test day" events, and create a list from them. Example here:[[BR]]
https://fedoraproject.org/wiki/QA/test/Fedora_20_test_days [[BR]]
And then it's included in the right column here:[[BR]]
https://fedoraproject.org/wiki/QA/Test_Days

If fedocal implemented a way to filter events in its list view and link to it, we could filter events with "Test Day" in its title and display them in a similar manner. That would be a generic fedocal functionality and could be used by other teams as well, so it sounds nice. However, one of additional features of our wiki generation approach was a way to archive historical events (for past releases). With fedocal approach, in case our qa calendar got wiped we would lose all history, and that's not that great. Also, we wouldn't be able to style the list according to our preferences, it would be a plain calendar view. But yeah, I'm sure we could find some way, if pingou wanted to implement those fedocal changes.

It's just that we need something working soon, and the wiki generation script is ready, just the bot account is missing.

ok.

Would it be possible for you to give us the script and we just run it inside infrastructure? We already do that for a ambassadors script that updates the wiki every night... then we could just reuse the same user that script uses?

Any news here? Not sure what we decided... ;)

Oh sorry, I forgot to update this ticket. We don't need the bot account at the moment. Pingou implemented required changes in Fedocal (kudos), so we use Fedocal now for test day management.

Login to comment on this ticket.

Metadata