GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
N/A
SUSE Rancher
Score9.4 out of 10
N/A
Developed by Rancher Labs and now from SUSE, Rancher is open-source software that enables organizations to deploy and manage Kubernetes at scale, on any infrastructure across the data center, cloud, branch offices, and the network edge. Rancher centrally manages Kubernetes clusters across the organization in order to ensure security and accelerate transformation. Rancher is also available hosted. Hosted Rancher is a fully managed Rancher control plane - presented as the fastest, most cost…
Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
SUSE Rancher as a management tool becomes useful on a larger scale. Small deployments not so much. If someone also requires Kubernetes capacity or storage, Rancher is an excellent choice. Also, without Kubernetes' skills, it is unlikely that Rancher deployment is going to be a success. Then again if someone else is managing your Kubernetes capacity, setting up the software's capacity will yield greater control. Rancher is not a very integrated solution similar to others in the market.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
No possibility to snapshot Projects. You can snapshot and restore the whole Kubernetes cluster, but not a Project or Namespace. For this, you have to use external tools.
You cannot detach the Rancher-created Kubernetes clusters from Rancher management.
Overall it deserves an 8 out of 10. The platform is very easy to use as long as the UI is stable. We have had a few buggy versions in the past. However the CLI is excellent and the platform is simple to manage and maintain. It is easy to deploy and offer for company wide use which increases utilization and ROI.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
The documentation is quite complete and there is a very active community that is willing to collaborate and answer questions for those who are just starting out.
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
We started using SUSE Rancher in the early days and spent a large amount of time getting to know and love it. This was before the days of some of the likes of Amazon Web Services who may now provide a cheaper but less feature-rich alternative to SUSE Rancher, however we have yet to explore this.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
The investment for small environments is quite significant. There has to be a compelling case to enhance the areas where SUSE Rancher brings in value to make such a financial leap. There is also a free version to test the value propositions, which will help support the user's buying decisions. More clusters, more volume, more tasks and more complexity in the environment equals more value that Rancher can provide.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Shortens "Time-to-Market" factor for new business applications or implementing new functionalities. From 1 to 50 microservices-based business applications in 6 years.
24/7 availability, generates more money. There are many infrastructure components that are regularly powered-off for maintenance or upgrade, bur we rarely are turning off our downstream Kubernetes clusters where our business applications lives.
Single Point of Contact with platform maintenance and development Team, eases implementation of new business applications
