create a pipeline to fullfill "what Thoth knows about your project" teaser feature

thoth-station / core

Using Artificial Intelligence to analyse and recommend Software Stacks for Artificial Intelligence applications.

https://thoth-station.github.io/

GNU General Public License v3.0

28 stars 25 forks source link

create a pipeline to fullfill "what Thoth knows about your project" teaser feature #314

Closed goern closed 2 years ago

goern commented 3 years ago

Is your feature request related to a problem? Please describe. in support of https://github.com/AICoE/meteor/issues/92 we deploy a service that will take a user repos, and create a PR containing a Thoth Advise. This is basically what Kebechet's thoth-advise manager does, but invoked in a different way.

High-level Goals A microservice and an Argo Workflow to implement this. SLO Metrics and a dashboard.

Describe the solution you'd like tbd

Describe alternatives you've considered tbd

Additional context This is an addition to the meteor UI that we could use as an ad during DevConf.US

Acceptance Criteria

[ ] document concept for already forked repos
[ ] implement service for initial fork/submission of a repo
[ ] define the interface between Thoth microservice and AICoE Meteor
[x] https://github.com/thoth-station/thoth-application/issues/1893
[ ] metrics about 'number of invocations of microservice (checked boxes)', 'created PR', 'accepted PR' is provided to be scraped
[ ] metrics are scraped by Prometheus and visualized by Grafana

goern commented 3 years ago

/triage accepted /assign @KPostOffice

goern commented 3 years ago

@harshad16 @KPostOffice maybe the artifact/service we deliver here is not a restful microservice, but a Tekton pipeline?!

sesheta commented 3 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 3 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/thoth-station/core/issues/314#issuecomment-921962028): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

codificat commented 2 years ago

Rotten issues close after 30d of inactivity.

this was not rotten back then - bot bug, fixed now /reopen /remove-lifecycle rotten

sesheta commented 2 years ago

@codificat: Reopened this issue.

In response to [this](https://github.com/thoth-station/core/issues/314#issuecomment-983643451): >> Rotten issues close after 30d of inactivity. > >this was not rotten back then - bot bug, fixed now >/reopen >/remove-lifecycle rotten Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

KPostOffice commented 2 years ago

/lifecycle active

goern commented 2 years ago

what is the status of this?

goern commented 2 years ago

any updates on this? do we consider it done?

KPostOffice commented 2 years ago

@goern @tumido We have an endpoint in user-api for running this type of request. How hard would it be to add this to meteor?

goern commented 2 years ago

@tumido ping

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

sesheta commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

sesheta commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/thoth-station/core/issues/314#issuecomment-1201754649): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

codificat commented 2 years ago

Reviewing if this was a legitimate closure or if this had to be reopened.

I believe that the functionality requested here is currently tracked in https://github.com/AICoE/meteor-operator/issues/43

Leaving this one as closed then.