Hudson CI (discontinued) vs. JRebel

Though it has a few setup issues, once you are done with setup it works like charm so one time setup issues won't bother. Reporting, version tracking, debugging everything is helpful and more clear and it reduces effort, in our scenario our QA team integrated their script with Hudson so that after every release it will get triggered automatically and developers will know if there is any major issue.

Incentivized

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.

Incentivized

• Oracle Hudson UI provides a simple setup and integration with SVN and other version control tools.
• The user control provides various operations to users through which it's easy to control the CI deployment process.
• It handles Performance testing and Automation testing, provides and accepts user interaction. Allows them to schedule jobs

Incentivized

• 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.

Incentivized

• The setup needs to be more user friendly, currently for first time users CI doesn't provide more guidelines.
• JMeter tool can be integrated but it's not easy, user has to follow and do research before setup. A simpler way would help make the process more user friendly.
• Selenium tool like JMeter can be integrated, if its Webservice it's easy but for UI automation integration not enough information is provided.

Incentivized

• It worked great, no big cons

Incentivized

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.

Incentivized

Oracle CI in terms of setup lags behind all above products, but then its use is also limited to release management so we can't really compare. Majority of organizations have dedicated team to help with CI Process so they take care of managing all jobs and setup.

Incentivized

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.

Incentivized

• Provides an easy way to deployment process
• Centralizes control for all release management
• Secured process, a user can only check errors and release management can take control of deployment. User roles are provided.

Incentivized

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

Incentivized