CloudBees Unify: Editions
CloudBeesExternal reviews
636 reviews
from
and
External reviews are not included in the AWS star rating for the product.
System Director
What do you like best about the product?
I can see 100% of the traceability of our changes
What do you dislike about the product?
That the Jenkins version is more well-known than the enterprise version
What problems is the product solving and how is that benefiting you?
Traceability of the changes and orchestration of them
Recommendations to others considering the product:
Integration with Kubernetes
Adapts to the needs of the area of operations in a simple way.
What do you like best about the product?
The centralized control that offers you over the masters, which you can deploy on new platforms such as kubernetes, user management and roles.
What do you dislike about the product?
The configuration on new platforms (kubernetes) is complicated.
What problems is the product solving and how is that benefiting you?
The way and speed of deploying changes to production is changing.
Seemless integration of slaves and clientmasters to one single operations center
What do you like best about the product?
Single sign on from Operations Center, Shared cloud and Shared agent features.
What do you dislike about the product?
Unable to configure multiple aws account when it comes to AWS plugins.
What problems is the product solving and how is that benefiting you?
Centralized way to manage multiple standalone jenkins. Collectively manage slave using Shared cloud / Shared agent feature. Everything can be managed from Operations center. We dont need to individually check each client masters to manage nodes.
Recommendations to others considering the product:
If an organization has single AWS account, then CloudBees core is good for them in all aspects. CloudBees modern platform is easy to setup and new modern UI is visually appealing. Easy to integrate with Gitlab and other tools. If an organization does not have LDAP, they can still use google SSO.
Simple, lightweight, effective
What do you like best about the product?
So far, my team and I have zero complaints about Rollout. The SDK was simple to install and it "just works" with minimal effort (speaking as a developer). In a few hours, I was able to set it up and start setting up A/B testing in our staging environment from specs provided by our product team. Can't ask for much more than that!
What do you dislike about the product?
To be honest, in a few months of using Rollout, I haven't run into any downsides to using it. There were no issues in the setup process, and the few minor questions I did have were answered promptly by the support team, even during the initial trial period.
What problems is the product solving and how is that benefiting you?
We're conducting A/B testing of new features and tweaks to existing features to improve our UX. So far, we've gathered measurable data which has helped in guiding my team in drafting new features based on the increased understanding of our user base.
Recommendations to others considering the product:
In my opinion, it's lightweight and as extendible as one desires. Its tagging system has given my team the flexibility it needs to implement everything we've been expected to build so far, and I can't currently think of a scenario in which it will be deficient in any way for our needs.
Cloudbees saved my a$$ on my upgrade on our new server (my first upgrade killed the old server)
What do you like best about the product?
The cloudbees support representatives are well versed and knowledgable. They often will fill in the gaps that the Jenkins and plugin documentation have, especially when the person trying to work through it is not a Java programmer -- like me. It's been a challenge at times decifering where things go. But everytime I have had a question, I have been able to ask someone at Support, and received an answer quickly. I have learned alot about the Jenins system in the few months we have had Jenkins Support.
I love their attention to detail and step by step instructions. One of the first tickets I opened with them was to perform an upgrade to our current jenkins system. I received back a laundry list of things to check, steps to take, and the availability of a 30 minute phone call to review any questions or concerns I had with the process / procedure.
I love their attention to detail and step by step instructions. One of the first tickets I opened with them was to perform an upgrade to our current jenkins system. I received back a laundry list of things to check, steps to take, and the availability of a 30 minute phone call to review any questions or concerns I had with the process / procedure.
What do you dislike about the product?
Sometimes, the documentation can lack certain information, like where the file is that you need to update, or how to execute a specific script.
What problems is the product solving and how is that benefiting you?
I needed to add specific functionality to give my team the same capabilities we had on our original jenkins installation (that I trashed and only partially restored) after we merged our work with another department's Jenkin's installation.
CJS gave me the details on the plugin I needed to add, and then helped me plan out my upgrade with specific step by step instructions to ensure that I had a rollback plan in case there was an unexpected conflict or issue during the upgrade.
This was especially meaningful for me as our group had previously been using a very old version of Jenkins that I attempted to upgrade prior to obtaining a support contract with Cloudbees. The upgrade attempt crashed the server, and it took several days to get the server back up and running. At that point, I was still having issues with Jenkins and finally was able to get the program up and stable enough to provide only the most basic services.
As I learned more about jenkins, and what we could do I realized that we would need a more up to date solution. That was when I discovered that another department in ITS had a jenkins installation. I arranged for us to work with them, and we moved our projects over to be handled on that server. Unfortunately, in doing that, we lost an importatant piece of functionality that we had on our old decrepit jenkins server -- auto code deployment.
And thus began the work to upgrade the new Jenkins server, which I am thrilled to say went off without a hitch!
CJS gave me the details on the plugin I needed to add, and then helped me plan out my upgrade with specific step by step instructions to ensure that I had a rollback plan in case there was an unexpected conflict or issue during the upgrade.
This was especially meaningful for me as our group had previously been using a very old version of Jenkins that I attempted to upgrade prior to obtaining a support contract with Cloudbees. The upgrade attempt crashed the server, and it took several days to get the server back up and running. At that point, I was still having issues with Jenkins and finally was able to get the program up and stable enough to provide only the most basic services.
As I learned more about jenkins, and what we could do I realized that we would need a more up to date solution. That was when I discovered that another department in ITS had a jenkins installation. I arranged for us to work with them, and we moved our projects over to be handled on that server. Unfortunately, in doing that, we lost an importatant piece of functionality that we had on our old decrepit jenkins server -- auto code deployment.
And thus began the work to upgrade the new Jenkins server, which I am thrilled to say went off without a hitch!
Recommendations to others considering the product:
If you are running your own Jenkins server and using it for critical functions, it is well worth having a support contract. The money you spend today will save you misery tomorrow.
Using Cloudbees Jenkins Distribution in a small instance for development purposes
What do you like best about the product?
Knowing that it is stable, backed by Cloudbees, and can upgrade to a supported instance more easily (which I've recommended we do). I also like the Jenkins advisor, assurance program, and beekeeper upgrade assistant.
What do you dislike about the product?
For our small instance, we went with a docker image of cloudbees. Upgrades aren't complicated, but would be nice to do them directly from the GUI all the time. When I did perform an upgrade, I ended up losing some data (some build history).
What problems is the product solving and how is that benefiting you?
build automation and continuous integration helps increase productivity and find issues early
Flow has transformed the speed and quality of our deployments
What do you like best about the product?
Flow comes with a great Graphical Interface, I particularly like the Pipeline view. There are many standard deployment options and plug-ins making custom scripts a thing of the past. The support team are extremely helpful.
What do you dislike about the product?
Navigating around Flow was not intuitive at first, but once experienced, it became easy.
What problems is the product solving and how is that benefiting you?
Quick automatic deployments, benefits are speed, quality, and the exclusion of manual intervention.
Recommendations to others considering the product:
Related above - Flow is relatively simple to set up and get productive, other products with less features will require more investment in set up and maintenance.
Very good tool
What do you like best about the product?
It has covered all our deployment automation needs, and we haven't used all its capabilities yet!
What do you dislike about the product?
Maybe, not being able to have an easy count of the used agents that we have in our license.
What problems is the product solving and how is that benefiting you?
Deployment automation in all our environments, including production, for our the layers in our architecture.
Task automation for the Operations teams.
Task automation for the Operations teams.
Great software and a really great experiance
What do you like best about the product?
Ease of use along with the documentation on how to use is very understanding and had no problem launching it.
What do you dislike about the product?
Really there is nothing that is a dislike - maybe pricing as it was a little pricey for our taste since we only had a hand full of users using it.
What problems is the product solving and how is that benefiting you?
We are making progress with just a little more than 3 months of using the software. I would say that within the next 3-6 months we will have a better idea.
Exactly what a development team needs, does one thing and does it very well. simple
What do you like best about the product?
How we can create configuration on the fly with new feature flags written in the code. Also hopefully soon bitbucket configuration in the repo configuration storage.
What do you dislike about the product?
Not having a sold feature (the backup of the flags to source repository) and having to wait for it.
What problems is the product solving and how is that benefiting you?
continuous delivery and hiding of not done features using the feature flags.
Recommendations to others considering the product:
Rollout will help your team be able to release code while keeping it out of mainstream until you want it, so very very easy to use. I liked being able to have developers write the feature flag in the code and have it go live then. Also the toggle overlay that you can use to override the flags for QA is amazing. I also like the smart features where you can single the flags to a single user or use a regex. The browser data is also abstracted away from the user so the flag settings are more secure.
showing 171 - 180