Jenkins Vs Rundeck

2,833 views
Skip to first unread message

shunmu...@gmail.com

unread,
Sep 23, 2013, 2:26:58 AM9/23/13
to rundeck...@googlegroups.com
Hi,

I need to convince by highlighting features in RD against Jenkins.

I found few like

  1. RD is Agentless.
  2. RD has pluggable built-in support for remote command execution.
  3. Dynamic Parameterization in Jobs.
  4. Ability to load option data from external sources.

Could you please me with more features.

Regards

Shunmugaraja

Moses Lei

unread,
Sep 24, 2013, 1:19:16 PM9/24/13
to rundeck...@googlegroups.com
Jenkins is fundamentally not a deployment tool, although it can be used like one. The architecture of it is quite focused around VCS revisions and builds, and in itself can't encapsulate flexible procedures across multiple environments. (For example, no node tagging, external node data source, etc).

Generally Jenkins is great for doing builds and kicking off smoketest/automated test deployments. I generally use it in combination with RunDeck or some other deployment tool in order to get the advantages of each. I wouldn't use Jenkins to deploy to production, to me it just isn't designed to do that.

--
Moses Lei
Principal, Village Chime LLC
mobile: +1 703 901 5969 | skype: moseslei | yahoo: moseslei


--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Nick Tkach

unread,
Sep 24, 2013, 3:23:40 PM9/24/13
to rundeck...@googlegroups.com
Not sure what you mean exactly by "I need to convince".  Are you looking for reasons to use Rundeck for a particular job as opposed to using Jenkins for the same job?

If so, then I agree with the user below.  You *can* force Jenkins to do things like deploying and running ssh scripts remotely, but it's definitely not the best use.  I've also found that generally Jenkins you want to use for things that are specifically build-related.  Things like checkouts, compiling, testing, and *maybe* copying the files out to servers somewhere.  There is a really nice plugin to go from Jenkins to Rundeck which makes it trivial to call whatever Rundeck job you need from Jenkins.  I'd suggest trying to outline the steps of the process you're trying to automate and figure out which make more sense to do on a build server (put those in Jenkins) and which make more sense to do on an application server (put those in Rundeck). 

Hopefully that helps some.
Reply all
Reply to author
Forward
0 new messages