<p>Jenkins can work just fine for this purpose.  In my view, Jenkins is a general-purpose automation tool, not necessarily a CI/CD tool specifically.</p>
<p>I'm on an Ops team and we use both Jenkins and Rundeck.  We generally prefer Jenkins because we find it difficult to navigate the Rundeck UI and find things like job output, but on the other hand it's often easier to write jobs for Rundeck, because you don't need to know Groovy/Pipeline.  Here are some examples of what we use each for:</p>
<ul>
<li>Install package updates on managed systems (yum/dnf packages) - Rundeck</li>
<li>Deploy &amp; provision new VMs - Jenkins</li>
<li>Run Chef on managed systems - Rundeck</li>
<li>Clean up stale Computer objects in Active Directory - Rundeck</li>
<li>Clean up stale subscriptions in Red Hat Satellite - Rundeck</li>
<li>Create &amp; configure new repositories in Bitbucket from templates - Jenkins</li>
<li>Build new vagrant images - Jenkins</li>
<li>Backup &amp; upgrade some services that my team manages (AWX, Red Hat Satellite, etc.) - Jenkins or Rundeck depending on the service</li>
</ul>
<p>I'm not claiming that either of these tools is the best choice for any of these particular examples, just that my team uses them for these purposes and they generally work well.  Historically, which tool we use for each job generally has come down to personal preference of the person who created the job.</p>
<p>In terms of the name of this type of tool, we just call them &quot;automation tools&quot; or &quot;automation platforms&quot;.  I'm not sure if there's a more &quot;industry-standard&quot; term for this type of tool.</p>

CC BY-SA 4.0
2021-03-12T10:09:17.607Z
This is a really helpful answer, thank you
Matt Harrison
CC BY-SA 4.0
2021-03-11T17:30:56.113Z
2021-03-11T17:30:56.113Z
jayhendren
<p>We have an operations team that looks after our running tenants. They respond to requests and incidents from users by following specific processes, they might for instance restart a container on an instance or undelete a resource a user deleted by accident.</p>
<p>Because these are repeatable actions they should be automated by rolling them into scripts. We want the jobs to be executed centrally so we can be able to track who ran which job and ideally have a central dashboard.</p>
<p>I need to investigate a platform to provide to the Operations team to get this job done.</p>
<p>Being from a dev background Jenkins would be my obvious choice but I feel like this must be a solved problem in the devops/ops world.</p>
<p>I've tried to research this but part of the problem is I don't know the name of the <em>class</em> of tool I'm looking for. When I look for automation platforms I find CI systems but they don't really fit with my problem.</p>
<p>Which tool or type of tool is appropriate to my needs?</p>

CC BY-SA 4.0
2021-03-10T23:41:25.690Z
short answer: something like [rundeck](https://www.rundeck.com/open-source).
Bruce Becker
<jenkins><operations>
What tool or type of tool am I looking for?
Matt Harrison
# What tool or type of tool am I looking for?

(Asked by: username_0 on 2021-03-10)

We have an operations team that looks after our running tenants. They respond to requests and incidents from users by following specific processes, they might for instance restart a container on an instance or undelete a resource a user deleted by accident.

Because these are repeatable actions they should be automated by rolling them into scripts. We want the jobs to be executed centrally so we can be able to track who ran which job and ideally have a central dashboard.

I need to investigate a platform to provide to the Operations team to get this job done.

Being from a dev background Jenkins would be my obvious choice but I feel like this must be a solved problem in the devops/ops world.

I've tried to research this but part of the problem is I don't know the name of the *class* of tool I'm looking for. When I look for automation platforms I find CI systems but they don't really fit with my problem.

Which tool or type of tool is appropriate to my needs?

**Tags:** jenkins, operations

> **Comments:**
> **username_1**: short answer: something like [rundeck](https://www.rundeck.com/open-source).  

---

## 1 answers

### Answer by username_2 on 2021-03-11. Score: 4 | Accepted answer

Jenkins can work just fine for this purpose. In my view, Jenkins is a general-purpose automation tool, not necessarily a CI/CD tool specifically.

I'm on an Ops team and we use both Jenkins and Rundeck. We generally prefer Jenkins because we find it difficult to navigate the Rundeck UI and find things like job output, but on the other hand it's often easier to write jobs for Rundeck, because you don't need to know Groovy/Pipeline. Here are some examples of what we use each for:

* Install package updates on managed systems (yum/dnf packages) - Rundeck
* Deploy & provision new VMs - Jenkins
* Run Chef on managed systems - Rundeck
* Clean up stale Computer objects in Active Directory - Rundeck
* Clean up stale subscriptions in Red Hat Satellite - Rundeck
* Create & configure new repositories in Bitbucket from templates - Jenkins
* Build new vagrant images - Jenkins
* Backup & upgrade some services that my team manages (AWX, Red Hat Satellite, etc.) - Jenkins or Rundeck depending on the service

I'm not claiming that either of these tools is the best choice for any of these particular examples, just that my team uses them for these purposes and they generally work well. Historically, which tool we use for each job generally has come down to personal preference of the person who created the job.

In terms of the name of this type of tool, we just call them "automation tools" or "automation platforms". I'm not sure if there's a more "industry-standard" term for this type of tool.

> **Comments:**
> **username_0**: This is a really helpful answer, thank you  

---

