Every 2 Minutes Cron Expression for Jenkins
*/2 * * * *Try it live
Valid
MINMinute
0HRHour
9DOMDay of Month
*MONMonth
*DOWDay of Week
1-5In plain English
At 09:00 AM, Monday through Friday
English → Cron
Try: "every 5 minutes", "every weekday at 9am", "every Monday at 3pm", "every month on the 1st"
Next 10 Executions
UTC- 1Mon, May 18, 09:00 AM UTCin 3d
- 2Tue, May 19, 09:00 AM UTCin 4d
- 3Wed, May 20, 09:00 AM UTCin 5d
- 4Thu, May 21, 09:00 AM UTCin 6d
- 5Fri, May 22, 09:00 AM UTCin 7d
- 6Mon, May 25, 09:00 AM UTCin 10d
- 7Tue, May 26, 09:00 AM UTCin 11d
- 8Wed, May 27, 09:00 AM UTCin 12d
- 9Thu, May 28, 09:00 AM UTCin 13d
- 10Fri, May 29, 09:00 AM UTCin 14d
crontab entrybash
# Add to crontab with: crontab -e
0 9 * * 1-5 /path/to/your/script.shWhen to use this schedule
- ▸ Polling an external API that enforces a 2-minute rate limit
- ▸ Checking for new messages in a queue with low-latency requirements
- ▸ Rotating or flushing in-memory caches before they grow stale
- ▸ Lightweight availability checks on an endpoint that doesn't need per-minute precision
Platform Syntax Comparison
The same "Every 2 Minutes" schedule expressed in every major platform's cron syntax.
| Platform | Expression |
|---|---|
| Standard Linux/Unix | */2 * * * * |
| GitHub Actions | */2 * * * * |
| Google Cloud Scheduler | */2 * * * * |
| Kubernetes CronJob | */2 * * * * |
| Azure Functions (NCRONTAB) | 0 */2 * * * * |
| AWS EventBridge | */2 * * * ? * |
| Quartz Scheduler | 0 */2 * * * ? |
| Spring @Scheduled | 0 */2 * * * * |
| Jenkins | */2 * * * * |
| Apache Airflow | */2 * * * * |
Frequently Asked Questions
Does */2 run at :00, :02, :04... or at some other offset? ▾
Yes — "*/2" in the minute field means every even minute: 0, 2, 4, 6 ... 58. It always aligns to the start of the hour.
What if I want it to run at :01, :03, :05 instead? ▾
Use "1-59/2" in the minute field to start at an odd offset.