What users are saying about
Top Rated
238 Ratings
9 Ratings
Top Rated
238 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.3 out of 101
9 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 9.8 out of 101

Likelihood to Recommend

Jenkins

Jenkins is open source, thus has a large number of plugins rolled out already. All major VCS, SCM, Git, and Maven applications support Jenkins. They even support Docker which is trending in DevOps nowadays. It has more than 50 APIs and plugins to work on. Thus, it is always appropriate to have Jenkins when you have a distributed workforce and to sync with everyone. To avoid synchronization problems in the distributed workforce and development, we use Jenkins. Code pushed to VCS can be built over another system so as to deploy in the production/release.
No photo available

JRebel

I recommend JRebel for Java developers, it will remove the time needed for redeployment, it will increase the focus on the task at hand (without being distracted by the redeployment) and will make them happier. I recommend JRebel for Java Development Managers, they should purchase this for their teams - it will increase productivity, decrease the product's time to market, and it will save money for the company. The ROI can be calculated upfront and presented to higher level management for approving this, if needed.
Cristian Bodnarasec profile photo

Pros

Jenkins

  • Automatic jobs: there are infinite possibilities when it comes to Jenkins. You can run code against any testing suite you can imagine or conjure up. You can deploy applications at any time anywhere, automatically with no human intervention. If a certain stage fails, it will notify the team and your sysadmin of the issue so you can resolve it as quickly as possible
  • Automatic rollback: because of how Jenkins works, it can hold off publishing code and integrate locally to run QA procedures before pushing to deployment. This means that bugs are caught before your servers are updated and prevents a faulty program from affecting your downtime in the first place. Its a game changer for high availability.
Dylan Cauwels profile photo

JRebel

  • Deploys all layout changes consistently (when Instant Run was initially available, you couldn't tell if the change you made to a layout was actually being tested or not).
  • Doesn't require a full build as often as Instant Run when changing code.
  • Works with compile time annotation libraries like Realm, etc.
Ken Yee profile photo

Cons

Jenkins

  • When setting up plugins, it can be tricky when you run into errors as sometimes the errors are not explanatory.
  • Jenkins requires plugins for most tasks, it would be nice to see things that are needed for most installations to be out of the box. This would tie them into the product more nicely and hopefully make those plugins easier to use.
  • Lucky for us, we run a fairly monolithic codebase which makes unit testing easier to set up. However, research shows that setting up this type of testing for micro-services with Jenkins is problematic as you cannot test multiple services at once.
No photo available

JRebel

  • It worked great, no big cons
No photo available

Usability

Jenkins

Jenkins 5.0
Based on 2 answers
It's is fairly good but not perfect.
No photo available

JRebel

No score
No answers yet
No answers on this topic

Performance

Jenkins

Jenkins 8.9
Based on 7 answers
Sometimes I feel like I am using software developed at the '90s. The Jenkins functioning is amazing. It fulfills its role, but when we are talking about the user interface, it is something painful sometimes, and unfortunately, I didn't see investment and/or improvement on this part over the past few years. Another thing I couldn't forget to mention is about the ecosystem around Jenkins, there are a bunch of plugins, but due to this flexibility, we caught ourselves struggling with broken plugins several times.
Erlon Sousa Pinheiro profile photo

JRebel

JRebel 10.0
Based on 1 answer
The performance of JRebel is great. It is enabling the Java team to do hot re-deployments and it has to be transparent and fast for the user, otherwise the whole purpose of reducing wasted time with re-deployments doesn't make sense.Also the User Interface for License Server management and analytics loads fast and the navigation through pages is quick.
Cristian Bodnarasec profile photo

Support

Jenkins

Jenkins 4.0
Based on 1 answer
Forum posts are often unresponsed to for years.
No photo available

JRebel

No score
No answers yet
No answers on this topic

Alternatives Considered

Jenkins

Travis CI and AppVeyor are good services that provide rudimentary support for builds, but they focus on Linux/OSX and Windows respectively, meaning that cross-platform builds will need to use both services. They are free for open source projects on GitHub, so they are seen quite frequently in the wild. They're easy to use and do a great job for simple projects, but have limitations that quickly become apparent for larger projects. Out-of-the-box, there's a limited ecosystem of tools available on these systems, though for Linux builds on Travis, builds can be run inside a Docker container, yielding greater flexibility and reproducibility. Docker and Drone are great alternatives that are container-native technologies but they are Linux only.
Jonathan Yu profile photo

JRebel

Hot code swapping doesn't have many players...it's mainly JRebel. We use JRebel a lot in our backend code development where it minimizes our development cycle (20min down to 30sec). For Android, the competitor is Android Studio's Instant Run which works fairly well now. For smaller apps, Instant Run is faster deploying but needs more full builds. With JRebel, you hardly ever need to do a full build.
Ken Yee profile photo

Return on Investment

Jenkins

  • Helps identify build issues right away, almost within minutes of something getting saved to SCM.
  • Helps managers (anyone really) deploy a daily build to QA for testing without needing additional dev resources.
  • Helps create versioned release builds quickly and consistently without needing additional dev resources.
Juan Ayala profile photo

JRebel

  • It sped up the developing time, and time is money for the company.
No photo available

Pricing Details

Jenkins

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

JRebel

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Add comparison