PeerSpot user
Business Intelligence QA Engineer at a tech vendor with 201-500 employees
Vendor
​Potential deployment problems pop up almost instantly during the development process.

What is most valuable?

  • Scalability
  • Controllability
  • Organization of jobs

How has it helped my organization?

Potential deployment problems pop up almost instantly during the development process. The developers are more confident about their committed code.

What needs improvement?

They need more useful tutorials about how to write database related plugins. It also needs a "run only" option without option for changing job configuration.

For how long have I used the solution?

I've used it for six months.

Buyer's Guide
Jenkins
March 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
768,886 professionals have used our research since 2012.

What was my experience with deployment of the solution?

There were some issues with deployment.

What do I think about the stability of the solution?

There were some issues with stability.

What do I think about the scalability of the solution?

There were some issues with scalability.

Which solution did I use previously and why did I switch?

No other solution was used previously.

How was the initial setup?

It wasn't complex.

What about the implementation team?

We did it in-house.

What was our ROI?

It's infinity as the developer's happiness are endless.

What's my experience with pricing, setup cost, and licensing?

It's free.

Which other solutions did I evaluate?

We did not do a deep evaluation but we did look at Bamboo.

What other advice do I have?

Stay calm and mind the gap between your QA automation team and developers.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user1057317 - PeerSpot reviewer
Lider de Diseño y Arquitectura de Soluciones with 11-50 employees
Real User
Enables us to automate many procedures like code review, testing, and deployment
Pros and Cons
  • "There are a large number of plugins available for integration with third party systems."
  • "The user interface could be updated a little."

What is our primary use case?

This solution is the primary component for our automatic release process, including code smell, integration, and deployment.

How has it helped my organization?

This solution has provided us with better quality and less time to market for our software products. We can also automate many procedures like code review, testing, and deployment.

What is most valuable?

There are a large number of plugins available for integration with third party systems.

What needs improvement?

The user interface could be updated a little. I think that a REST API is needed to expand the integration capabilities.

For how long have I used the solution?

One to three years.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Jenkins
March 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
768,886 professionals have used our research since 2012.
PeerSpot user
QA Automation Engineer at a tech services company with 1,001-5,000 employees
Real User
Nice functionality, but does not have a very user-friendly interface
Pros and Cons
  • "We used it for all continuous integration parts, like automation testing, deployment, etc."
  • "It does not have a very user-friendly interface."

How has it helped my organization?

We used it for all continuous integration parts, like automation testing, deployment, etc.

What is most valuable?

In Jenkins v.2, the most useful feature is the Pipeline plugin. The reason why I think so is that you can build your own workflow with Groove and the plugin has many useful features like parallel executing, running commands, etc. and even imagine implementing your own features on Groove.

What needs improvement?

The interface.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

Yes, in Jenkins v.2. However, I am guessing that is because we used it right after the first release.

What do I think about the scalability of the solution?

In my opinion, there is an issue with the scalability. After Jenkins has big count of jobs, it begins to lose performance and you need to start one more server with a separate Jenkins and migrate some jobs there.

How are customer service and technical support?

It was enough for me.

Which solution did I use previously and why did I switch?

No, I did not.

How was the initial setup?

As I remember, there was just one command on Linux. Pretty easy.

What's my experience with pricing, setup cost, and licensing?

It is free.

Which other solutions did I evaluate?

I didn't choose, but in my opinion, this is the best open source solution for CI and CD.

What other advice do I have?

Nice functionality, but does not have a very user-friendly interface.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user