argo
Cronicle
Our great sponsors
argo | Cronicle | |
---|---|---|
43 | 22 | |
14,259 | 3,276 | |
1.4% | - | |
9.8 | 7.5 | |
6 days ago | about 1 month ago | |
Go | JavaScript | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
argo
-
StackStorm – IFTTT for Ops
Like Argo Workflows?
https://github.com/argoproj/argo-workflows
-
Creators of Argo CD Release New OSS Project Kargo for Next Gen Gitops
Dagger looks more comparable to Argo Workflows: https://argoproj.github.io/argo-workflows/ That's the first of the Argo projects, which can run multi-step workflows within containers on Kubernetes.
For what it's worth, my colleagues and I have had great luck with Argo Workflows and wrote up a blog post about some of its advantages a few years ago: https://www.interline.io/blog/scaling-openstreetmap-data-wor...
-
Practical Tips for Refactoring Release CI using GitHub Actions
Despite other alternatives like Circle CI, Travis CI, GitLab CI or even self-hosted options using open-source projects like Tekton or Argo Workflow, the reason for choosing GitHub Actions was straightforward: GitHub Actions, in conjunction with the GitHub ecosystem, offers a user-friendly experience and access to a rich software marketplace.
-
(Not) to Write a Pipeline
author seems to be describing the kind of patterns you might make with https://argoproj.github.io/argo-workflows/ . or see for example https://github.com/couler-proj/couler , which is an sdk for describing tasks that may be submitted to different workflow engines on the backend.
it's a little confusing to me that the author seems to object to "pipelines" and then equate them with messaging-queues. for me at least, "pipeline" vs "workflow-engine" vs "scheduler" are all basically synonyms in this context. those things may or may not be implemented with a message-queue for persistence, but the persistence layer itself is usually below the level of abstraction that $current_problem is really concerned with. like the author says, eventually you have to track state/timestamps/logs, but you get that from the beginning if you start with a workflow engine.
i agree with author that message-queues should not be a knee-jerk response to most problems because the LoE for edge-cases/observability/monitoring is huge. (maybe reach for a queue only if you may actually overwhelm whatever the "scheduler" can handle.) but don't build the scheduler from scratch either.. use argowf, kubeflow, or a more opinionated framework like airflow, mlflow, databricks, aws lamda or step-functions. all/any of these should have config or api that's robust enough to express rate-limit/retry stuff. almost any of these choices has better observability out-of-the-box than you can easily get from a queue. but most importantly.. they provide idioms for handling failure that data-science folks and junior devs can work with. the right way to structure code is just much more clear and things like structuring messages/events, subclassing workers, repeating/retrying tasks, is just harder to mess up.
-
what technologies are people using for job scheduling in/with k8s?
Argo Workflows + Argo Events
-
What are some good self-hosted CI/CD tools where pipeline steps run in docker containers?
Drone, or Tekton, Argo Workflows if you’re on k8s
-
job scheduling for scientific computing on k8s?
Check out Argo Workflows.
- Orchestration poll
- What's the best way to inject a yaml file into an Argo workflow step?
-
Which build system do you use?
go-git has a lot of bugs and is not actively maintained. The bug even affects Argo Workflow, which caused our data pipeline to fail unexpectedly (reference: https://github.com/argoproj/argo-workflows/issues/10091)
Cronicle
- Cronicle: Multi-server task scheduler and runner, with a web based front-end UI
-
Executing Cron Scripts Reliably at Scale
Wasn't it simpler to use Cronicle (https://github.com/jhuckaby/Cronicle)?
-
Is there a Docker container, or self-hosted app to create and monitor cron jobs?
You can give cronicle a try. It has a web based UI and sone good stats.
- Cronjobs UI Service / CLI
-
Good Cron GUI
Have a look at Cronicle ( https://github.com/jhuckaby/Cronicle )
- Ask HN: How to monitor periodic short-lived processes?
-
How to setup a containerized python environment? Function as a Service or an alternative solution for a Python execution environment.
Firstly, I tried Rundeck and Apache Airflow. They are complete overkill for what I want to do. Then I found Cronicle which is light enough, besides it can pull double duty as a general purpose scheduler.
-
Selfhosted CRON Server + Webapp
Also check out http://cronicle.net/
-
A little note for those of you trying to run yt-dl & inbuilt title changing with cron jobs.
Would recommend https://github.com/jhuckaby/Cronicle for anyone running cronjobs but would like to have an interface. It has plenty of features, logs, resource stats, and notifications. Plus it's easy to setup.
-
Centralised web GUI for task scheduling?
Thought I'd post here before taking a dive into this and see if anyone has any practical experience. I'm looking for centralising scheduled tasks for multiple servers, preferably with a management GUI for friendliness. I found Crontab-UI which seems to only interact with the single host's crontab. Then I stumbled upon Cronicle which looks feature rich but looks like multi-server is handled by deploying the GUI to each host. A central server + agents on each host would be nicer. I'm wondering if anyone uses Cronicle, or another solution? Thanks!
What are some alternatives?
temporal - Temporal service
Airflow - Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
keda - KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
node-cron - Cron for NodeJS.
crontab-ui - Easy and safe way to manage your crontab file
flyte - Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
Rundeck - Enable Self-Service Operations: Give specific users access to your existing tools, services, and scripts
StackStorm - StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html
jellyseerr - Fork of overseerr for jellyfin support
n8n - Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
OliveTin - OliveTin gives safe and simple access to predefined shell commands from a web interface.