Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move validation cron-job(s) from PSI to MP+ #437

Open
2 tasks done
jpopelka opened this issue Jan 20, 2023 · 3 comments
Open
2 tasks done

Move validation cron-job(s) from PSI to MP+ #437

jpopelka opened this issue Jan 20, 2023 · 3 comments
Assignees
Labels
complexity/single-task Regular task, should be done within days.

Comments

@jpopelka
Copy link
Member

jpopelka commented Jan 20, 2023

In order to know how to proceed with the packit/private#13 (MP+) it'd be nice to have an overview of how demanding each subtask is, where we could potentially get stuck, what is a must and what's not so crucial, what we need to do first and what can actually wait. The easiest is to go through the process with something small and easy - the validation cron job(s).

Tasks will be added step by step.
Let's start with:

@jpopelka jpopelka added the complexity/epic Lost of work ahead, planning/design required. label Jan 20, 2023
@jpopelka
Copy link
Member Author

Closing, we'll continue in packit/private#13

@mfocko
Copy link
Member

mfocko commented Aug 31, 2023

Reopening with regards to decommissioning of the PSI instance where we run validation.

Though it might make sense to consider moving to one of the instances that will be proposed to the affected projects. (Running validation from the same instance where the service resides doesn't help in case of an outage of the service itself.)

cc @lbarcziova from the Slack discussion

@mfocko mfocko reopened this Aug 31, 2023
@lbarcziova
Copy link
Member

Running validation from the same instance where the service resides doesn't help in case of an outage of the service itself.

+1, it would be the best to have it somewhere separate, let's wait for the proposed instances in the mail thread and discuss then.

@mfocko mfocko added complexity/single-task Regular task, should be done within days. and removed complexity/epic Lost of work ahead, planning/design required. labels Nov 16, 2023
@majamassarini majamassarini self-assigned this Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity/single-task Regular task, should be done within days.
Projects
Status: done
Development

No branches or pull requests

4 participants