GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
N/A
meshIQ
Score 8.9 out of 10
N/A
meshIQ provides observability and management capabilities for middleware platforms, from modern Kafka-based streaming to legacy messaging technologies such as IBM MQ, across cloud and on-premises environments.
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.
If you're involved in any business that is related to banking, insurance and lending industry, take the short way and save yourself from thousands of wasted dollars on fraud detection and application management issues, Nastel is my savior and it's the most powerful killer solution to beat the fraud and have a winning application performance management, It's like hiring a mathematics magician with super powers to help businesses get over the delayed amount of time spent on a problem, and the average time to process a claim, reduce errors and most importantly to decrease the number of tickets at the help center for a better and higher customer satisfaction score.
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.
The UI needs a lot of improvements to meet today's standards while keeping the functional part highly performing as it used to be
Being unable to run reports through the workgroup security manager is a serious con, I think they need to consider giving it more attention
the auto-monitoring feature performance goes low when it's enabled during a heavy workloads, it leads to a lower/heavier performance, but during the latest update I feel it got lighter somehow.
They also need to give more attention to the encryption and enhance it with the latest encryption technologies
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.
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
