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

detect when no new commit/Hackage changes to avoid unnecessary runs #45

Open
juhp opened this issue Oct 11, 2024 · 0 comments
Open

detect when no new commit/Hackage changes to avoid unnecessary runs #45

juhp opened this issue Oct 11, 2024 · 0 comments

Comments

@juhp
Copy link
Collaborator

juhp commented Oct 11, 2024

Currently we just loop nightly and it keeps running build.sh (after 49min sleep currently) even if there are no changes.
This is a waste of resources, time and energy: we should skip when there are no changes since the last build.

However it is not trivial, we need to detect:

  • if Hackage was updated for any packages in Stackage?

or

  • if there were any new stackage commits?

No sure if there are any others important changing conditions.

Though with longer sleep times this might be less of an issue.

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

No branches or pull requests

1 participant