all the remaining issues were solved and the bot is now processing tickets as it should. I will watch the SCM request repository for next few days to see if everything is working as it should.
Thanks for your patience.
On behalf of CPE Team,
Michal
On 10. 01. 23 18:29, Michal Konecny
wrote:
Most of the issues are resolved now. There is one remaining ticket [0] that is returning 500 on branch creation. I will continue investigation on this ticket tomorrow.
I'm sorry for the rough start.
On behalf of CPE Team,
Michal
[0] - https://pagure.io/releng/fedora-scm-requests/issue/50370
On 10. 01. 23 13:52, Michal Konecny wrote:
Hi everyone,
after deployment we had some issues with API tokens for src.fedorapoject.org and pagure.io. Those issues are now solved.
Only one issue remains and that is missing list of epel9 packages on https://infrastructure.fedoraproject.org/repo/json
We are currently working on that.
All the epel9 branch requests will fail right now, we will reprocess them once this is fixed.
On behalf of CPE Team,
Michal
On 10. 01. 23 12:26, Michal Konecny wrote:
Hi everyone,
this automation is now in place and new SCM requests will be processed automatically. If you find any issue with the automation, please report it to toddlers issue tracker [0].
On behalf of CPE Team,
Michal
[0] - https://pagure.io/fedora-infra/toddlers/issues
On 08. 12. 22 11:10, Michal Konecny wrote:
Hello everyone,
for some time CPE (Community Platform Engineering) team is working on automating Fedora SCM requests [0]. The automation is currently live on staging. You can see the output (closed tickets) in Fedora SCM requests staging repo [1].
The automation is done using a plugin in toddlers [2]. We have a documentation [3] for the new toddler, if you want to know more about it. There is also a ticket [4] tracking this work.
We plan to deploy this in production on 10th January 2023, after that all the Fedora SCM request will be processed automatically and it will ping correct people if the manual intervention is needed. This will not change anything in user workflow, it will just make the job of Fedora Release Engineering Team easier and let them focus on other things.
On behalf of CPE Team,
Michal
[0] - https://pagure.io/releng/fedora-scm-requests
[1] - https://stg.pagure.io/releng/fedora-scm-requests
[2] - https://pagure.io/fedora-infra/toddlers
[3] - https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
[4] - https://pagure.io/releng/issue/9274
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
