Small recurrent tasks, long processing jobs, integration scripts, everything runs in Eventline
What is the advantage of this? For example, an "integration script" is a kind of re-occurant QA test? wouldn't that be better run in a CI (that has repo context) or even a tool like sonarqube that can you graphs of change over time, or a tool that provides a UI specific to the test framework?
To take your example: "CI/CD platforms make it easy to script tasks related to a repository, but are limited when trying to do anything else"
Isn't that a good thing? keep technical repo related stuff (e.g. build a package/image) in the CI - even if it's a call to some other system, or ansible script.
On that note, you could run Ansible AWX/tower and run a lot of things from that - how does Eventline compare?
Eventline lets you schedule any script; you can of course build and test software, but you can also run recurring data import or processing jobs, report generation, backups, monitoring checks (I have multiple jobs regularly verifying properties of live systems)…
Since you can add parameters to your jobs and run them manually with an auto-generated form, it becomes very simple to create complex tasks and let colleagues use them. You could have tasks to create feature environments, prepare onboarding for new employees, process GDPR requests, all kinds of jobs really.
I do know anything about Ansible AWX, but looking at the documentation, the only thing I can think is that it seems awfully complex when I just want to be able to run script and have a platform to monitor what happens and alert me when it fails.
looking at the documentation, the only thing I can think is that it seems awfully complex
can you give an example of the added complexity (other than the dependency on ansible script language itself)? For example you mention "access to credentials" which is one of the complexity points.
Comments
What is the advantage of this? For example, an "integration script" is a kind of re-occurant QA test? wouldn't that be better run in a CI (that has repo context) or even a tool like sonarqube that can you graphs of change over time, or a tool that provides a UI specific to the test framework?
To take your example: "CI/CD platforms make it easy to script tasks related to a repository, but are limited when trying to do anything else"
Isn't that a good thing? keep technical repo related stuff (e.g. build a package/image) in the CI - even if it's a call to some other system, or ansible script.
On that note, you could run Ansible AWX/tower and run a lot of things from that - how does Eventline compare?
Eventline lets you schedule any script; you can of course build and test software, but you can also run recurring data import or processing jobs, report generation, backups, monitoring checks (I have multiple jobs regularly verifying properties of live systems)…
Since you can add parameters to your jobs and run them manually with an auto-generated form, it becomes very simple to create complex tasks and let colleagues use them. You could have tasks to create feature environments, prepare onboarding for new employees, process GDPR requests, all kinds of jobs really.
I do know anything about Ansible AWX, but looking at the documentation, the only thing I can think is that it seems awfully complex when I just want to be able to run script and have a platform to monitor what happens and alert me when it fails.
can you give an example of the added complexity (other than the dependency on ansible script language itself)? For example you mention "access to credentials" which is one of the complexity points.