This repository was archived by the owner on Dec 3, 2019. It is now read-only.
Adds the cron Whenever gem for daily runs of GitHub statistics rake task #257
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
todo: determine if any type of tests are needed. My opinion is that tests verifying that the gem works are not needed. I could be testing that the jobs listed in the config file exist, to prevent recurring hidden errors, and individually test the rake files based on what needs to be done. |
Member
|
With the migration to sidekiq worker classes instead of ActiveJob base classes closing this. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes
We need to be able to have recurring cron jobs ran, on our behalf. For example, to hit GitHub's API, or the Meetup API, on a daily basis, to pull in current statistics or Meetup events.
The whenever gem is a perfect tool to solve this.
This implements the backend.
In order for this to go live in prod, infrastructure will need to be added and addressed.
Issue Resolved
Fixes #163