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

Clean stale builds from state #171

Merged
merged 1 commit into from
Dec 30, 2024
Merged

Conversation

thatportugueseguy
Copy link
Collaborator

Description of the task

When running tests for the failed builds notifications I've noticed that if for some reason we don't get all the notifications for the events that happen in the followed repo, we will get stale builds. They stay in pending state and are not cleaned because we treat them as if they are still running.

This PR handles that issue by setting up a threshold for a build run time and cleaning up builds that passed that threshold.

Considerations

For the time being I have hardcoded a threshold of 2h, only as a value. It's definitely two long, but didn't want to assume 1h straight away.

At the same time, I think it makes sense to add this threshold to the .monorobot config file. I haven't done it because i'd like to discuss first what format we want to have that threshold in.

Nothing in these considerations is blocking for this PR to be merged.

@thatportugueseguy thatportugueseguy merged commit c7eea9e into master Dec 30, 2024
0 of 3 checks passed
@thatportugueseguy thatportugueseguy deleted the cleanup-stale-state branch December 30, 2024 12:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant