As previously announced on fedora-devel, I am working on a service that listens to fedora-messaging and for every new RHBZ review ticket or a new comment with updated packages, it submits a build in Copr. Copr automatically runs the fedora-review tool and generates the review.txt file. Once the build is finished, my service gets the message and generates a helpful comment (so far only to STDOUT).
I am planning to let it post the comments back to the RHBZ tickets.
Devel list Announce: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/E4TT2PEOSITJ4PJP44L2GQUU4CA6R6B3/
Upstream: https://github.com/FrostyX/fedora-review-service
I don't mind running the service on my own HW but at some point, better sooner than later, it would be great to deploy it within Fedora infrastructure. By this, I of course don't mean the fedora-infra team maintaining the service but rather running it in AWS, you guys having access to it and knowing about it, using ansible, etc.
Can you please give me a list of your requirements and expectations, so I can slowly start working on them?
Whenever it is convinient for you, no deadlines on my side.
Thank you very much, Jakub
Can we move this discussion to the mailing list?
I find tickets very bad for general discussion. I prefer they be left for 'do this exact thing'.
That said, I think this is a good candidate for you to develop and run in our communishift cluster and then when it's stable/solid/used a lot we can look at rolling it into our staging and production clusters. I don't think there's anything that would cause it to not work in openshift?
Metadata Update from @zlopez: - Issue priority set to: Waiting on Reporter (was: Needs Review)
Can we move this discussion to the mailing list? I find tickets very bad for general discussion. I prefer they be left for 'do this exact thing'.
Sure, no problem.
That said, I think this is a good candidate for you to develop and run in our communishift cluster > and then when it's stable/solid/used a lot we can look at rolling it into our staging and production > clusters. I don't think there's anything that would cause it to not work in openshift?
Okay, I will try to deploy in communishift and submit tickets regarding permissions, etc, if necessary.
Metadata Update from @frostyx: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
run in our communishift cluster
Is this the correct link to the CommuniShift? https://console-openshift-console.apps.fedora.cj14.p1.openshiftapps.com/
I found it here in the documentation https://docs.fedoraproject.org/en-US/infra/ocp4/sop_communishift/
If not, can you please point me to the right instance? Otherwise, I think I don't have sufficient permissions to use it - The button for creating a new project is grayed out.
Yes, that is the place... but we need to add a project for you. ;)
What would you like the project called?
We then create a communishift-$name group with you in it and as manager to add more people and you should get perms to create projects then. :)
Metadata Update from @kevin: - Issue status updated to: Open (was: Closed)
we need to add a project for you. ;)
Aha :-)
I would simply call the project fedora-review-service
fedora-review-service
I added your app, but the playbook has some issue.
I filed https://pagure.io/fedora-infrastructure/issue/11044 on that.
As soon as thats fixed your app should be ready to go.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thank you very much @kevin
Log in to comment on this ticket.