[Feature Request] Pass job frequency as argument to job
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 8.9k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
Description
We receive failures of cron jobs in our ticketing system. However, we don't have the context of the schedule.rb there. Obviously, we can just open the code and take a look, but it would be much more comfortable to immediately see how often the job is scheduled to run, because if a job running every 5 minutes fails, it's a whole different thing than having a job fail that runs once a month.
Is there currently a way to pass this job frequency (e.g. "every 30 minutes") into the job? If not, does anybody know the project well enough to estimate the complexity of building this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing schedule.rb and the job invocation path to determine whether the configured schedule can be passed into the job. Clarify the desired argument format and how schedules with different frequencies should be represented. Done means a defined approach for exposing the frequency to jobs, with the required behavior and scope agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100