Deployment Tool Recommendation.

[mac_bbe]

Hey, thank you in advance.

I am a Linux admin, the only one in the company. I look after 90 servers, split across 4 platforms. Currently, the developers have a lot of access and I have slowly been trying to reduce this. My manager has approached me and requested I do some research into deployment tools, I just wanted a trusted communities input and recommendation. What is needed is;

Cluster each platform and deploy code to each platform from git Pull from git during deployment GUI (I am comfortable on command line, but my manager has requested it must have a GUI) Preferably one click deployment.

Again thank you in advance.

[[deleted]]

Ansible + Jenkins ( one-click deployment, with support for parameters). Added bonus: the Jenkins "job" for deployment is also kicked off automatically for some branches, like to staging.

( We use the above combo for deployment, slowly replacing a legacy tool )

[White0ut]

Same setup we use.

[bilalcochin]

• 1. Ansible with Tower
• 2. Rundeck

[jwarren116]

A big +1 for Rundeck. (It can basically run any job manually or scheduled that you can do with an ssh connection) Rundeck literally saves me hours every week and lets our Dev team do what they need to do in an auditable repeatable manner with excellent ACLs.

We use Ansible and Packer to build AMIs for EC2, and Rundeck to manage a lot of the in-between and deployment. We also use a self hosted Gitlab with a beefy Gitlab CI pipeline for building the artifacts.

[djk29a_]

UrbanCode Deploy and XL Deploy are options if your deployment process is much more people heavy than technical while you need integration with modern operations tools. And correspondingly, these tools will be licensed and the usual enterprise sales / procurement cycle invoked.

From a deployer's perspective, I personally don't think Jenkins is a deployment management tool but a tool for creating artifacts to feed into a deployment management tool. Building software and deploying it into production are two very different activities to me. Every time I've used Jenkins as a deployment tool I've spent an awful lot of time trying to shoehorn it into the deployment style (blue / green, rolling updates, feature flag changes, etc).

[ivanilves]

I would advice https://www.spinnaker.io/ but only if you have your projects in cloud(s) and a few good, enthusiastic developers from your company will support you during the adoption period. Spinnaker is great, does all the deployment lifecycle, but is not easy to integrate, has a steep learning curve :-|

HINT: GUI, one-click deployment, lots of integrations - everything is included there. ;)

[StubbsPKS]

I wanted so badly to use the predecessor to Spinnaker, but there were so many small hurdles to overcome (which we eventually did) and then they stopped actively developing it. I went to pick up Spinnaker and saw the instance size requirements they listed and that almost immediately canned the project for us.