Sign in
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

It provides better visual reporting for the data

  • By DevOpsMa22d9
  • on 01/08/2019

We use it for migrating and scaling Jenkins infrastructure.
How has it helped my organization?
It provides better visual reporting for the data, whether it succeeded or failed. It also has a lot of plugins.
What is most valuable?
* It has a wide variety of plugins.
* It has a good reporting solution.
What needs improvement?
The integrations with Kubernetes has become challenging when it comes to scaling on a machine. We don't have the proper agent release to do this.
For how long have I used the solution?
Less than one year.
What do I think about the stability of the solution?
We haven't had any stability issues.
What do I think about the scalability of the solution?
We don't have any scaling issues. We have about 400 servers with three Jenkins masters.
How is customer service and technical support?
I would rate the technical support as an eight out of ten. We are receiving constant support from the cloud-based support team.
How was the initial setup?
With Kubernetes and the cloud-based configuration, it is a little tricky. We are still trying to figure out the best way to do it.
What was our ROI?
We have dedicated Jenkins masters for our different teams. This way, teams are not stepping on each others toes. They can build something and it is ready, then export their jobs to the main master.
What's my experience with pricing, setup cost, and licensing?
They need to improve the licensing. With a few of the companies, when you have the agent installed, once the instance dies, you are released from the license. However, with cloud-based, you have to contact the cloud-based support to release the license and map it to the new instance.
Which other solutions did I evaluate?
We looked at Jenkins and Bitbucket Pipelines. Since our developers were already used to the Jenkins infrastructure, we continued building on top of our previous platform using the cloud infrastructure.
We had been using Jenkins for the last six years and wanted to continue with the same type of infrastructure.
What other advice do I have?
I would recommend this product rather building your own homegrown solution.


There are no comments to display