BSD Ports

devel/rubygem-sidekiq-cron-rails-gitlab 2.3.1 MidnightBSD

Enables to set jobs to be run in specified time (using CRON notation)

System
MidnightBSD
Repository
mports
Maintainer
[email protected]
Last update
Commit
d3869390ee
License
mit
Categories
devel, rubygems

Description

Sidekiq-Cron is a scheduling add-on for Sidekiq.

It runs a thread alongside Sidekiq workers to schedule jobs at specified times (using cron notation * * * * * parsed by Rufus-Scheduler).

It also checks for new jobs to schedule every 10 seconds and doesn't schedule the same job multiple times when more than one Sidekiq worker is running.

Scheduling jobs are added only when at least one Sidekiq process is running.

In the other systems

SystemPortVersion
MidnightBSDdevel/rubygem-sidekiq-cron-rails-gitlab2.3.1
FreeBSDdevel/rubygem-sidekiq-cron-rails-gitlab2.4.0
DragonFlydevel/rubygem-sidekiq-cron-rails-gitlab1.12.0
HardenedBSDdevel/rubygem-sidekiq-cron-rails-gitlab2.3.1
GhostBSDdevel/rubygem-sidekiq-cron-rails-gitlab2.3.1

Install

Binary package:

mport install sidekiq-cron-rails-gitlab

From mports:

cd /usr/mports/devel/rubygem-sidekiq-cron-rails-gitlab && make install clean

To depend on this port in another port's Makefile:

RUN_DEPENDS=	sidekiq-cron-rails-gitlab>0:devel/rubygem-sidekiq-cron-rails-gitlab

Dependencies

As this port's Makefile names them.

Build 4

Runtime 4

Build dependencies 4
Run dependencies 4

No port depends on this one.

Configuration

No options to configure.

USES
gem
Service scripts
none

Files

distinfo 1
FileSizeSHA256
rubygem/sidekiq-cron-2.3.1.gem3020896ab3da372289a30dc744c1daa2ae2e85960b2444a6f6ed68df1ff7882c44aac
Master sites 1
  • RG

Commit history 1

DateCommitCreditsLog message
d3869390ee Lucas Holt devel/rubygem-sidekiq-cron-rails-gitlab: install RUN_DEPENDS at build time
The gemdeps QA check runs ${LOCALBASE}/bin/gem list, so the runtime gems have to be installed before fake-qa. The build cluster installs BUILD_DEPENDS but not RUN_DEPENDS, so the check reported dependencies as unsatisfied even though they had built successfully in the same run. This matches the convention already used by most rubygem ports. AI-Assisted-by: Claude Opus 5 (1M context) <[email protected]> Signed-off-by: Lucas Holt <[email protected]>