Azure Pipelines vs. JRebel

With a fully Microsoft Azure based workflow - Azure Pipelines makes absolute sense. Azure Pipelines are robust and work very well with SonarQube for test coverage and are shared with our developers. This prevents the developers for pushing code without unit tests across our backend and frontend platforms. We have reduced our instances of manual regression tests especially when there are multiple teams working across the same repositories.

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

• Code Integration/Code Deployment
• Azure Engine Auto Scaling Up with help of Pipeline
• Managing Version Control and deploy in rollback with just one click

Incentivized

• Removes the time needed for redeployments of the source code - improves productivity, time to market, and saves money.
• Easy to install
• License renewals - the sales department reaches out to you long before the licenses expire so you can have time to get your approvals.
• Analytics and reporting - it will show you the time saved by JRebel and even the ROI, if you input the average hourly cost of a developer.

Incentivized

• Error messaging when team members don't have permissions

Incentivized

• Launch times are where JRebel is slower than Instant Run.
• Sometimes, it has incompatibilities with how you wrote something and causes compile failures, but Zero turnaround is quick to respond.

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

We have used the GitHub CI/CD. Earlier we were using the Azure Pipelines but after GitHub had their actions, we integrated that for CI/CD. It runs the tests and makes a production build which can be live. GitHub CI/CD is more useful because we have to make script only once then just by few changes we can deploy it onto Azure, AWS, Google anywhere so we found it more convenient

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

• We don't have to deploy changes manually
• But because of this that we automated some tasks, we need to be still aware of some edge cases we can meet and which can cause a pipelines failures
• We can deploy changes pretty fast

Incentivized

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

Incentivized