Codefresh vs. JRebel

While deploying docker images on kubernetes pods I must say Codefresh helped me a lot. It has made my work easy as an Automation tool. I can setup a simple pipelines to automate my build for kubernetes. but for more complex pipelines Codefresh need some improvement

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

• Continuous Integration and Continuous Development. we can setup jobs that automatically triggered when there is any changes in code and starts building up the build images automatically and then pushing images to Container Registry
• We can involve Version control system like github, bitbucket, gitlab etc for integration of Codefresh with our code stored in these Version control systems.
• On the failure of any jobs/pipeline Codefresh can also send Notification on our email.

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

• With Codefresh it's become hard to handle complex pipelines
• Need to focus more on Documentation part
• UI can be more attractive
• Security can be more increased

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

It's very scalable It is cost effective It easily get integrated with third party tools It easily get integrated with Kubernetes Docker.

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

• Positive:
• As an Automation tools I must say it has reduced manual labour , reduced errors and improved quality of work.
• It easily get integrated with third party tools which increases ease ness in our work
• Negative:
• Although being a very good tools in CI/CD
• It requires improvement in UI, it's speed, security, optimization.

Incentivized

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

Incentivized