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

Refactor how commitalert handles a new job #356

Open
tomrittervg opened this issue Mar 27, 2024 · 0 comments
Open

Refactor how commitalert handles a new job #356

tomrittervg opened this issue Mar 27, 2024 · 0 comments
Labels
Enhancement New feature or request Medium

Comments

@tomrittervg
Copy link
Collaborator

In vendoring.py for vendoring tasks, we refactored things so that the first thing we ever do is create a job in the table. This means that if something goes wrong, we won't try continually processing the job.

We don't have the same design for commitalert tasks. (They're a lot rarer, so this hasn't ever come up.) We should probably change how commitalert works so it works similarly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Medium
Projects
None yet
Development

No branches or pull requests

1 participant