Azure Resource Manager vs. Gradle Build Tool (Open Source)

I solve lots of problems with ARM, We have developed 3 architectures for clients using templates, with the deployment of Azure resources (gateways and load balancers) Its main and best feature is Infrastructure and automation management(extraction load and transformation )ETL, And management of resources via the cloud for platforms, SO that the analytics with its best feature intuitive portal which is very User friendly.

Incentivized

Gradle Build Tool is more suitable with the Java projects. It has helped us to automate the build part of the devops cycle. Its configuration and Groovy script is really easy to understand and can be implemented with ease. It can be used both for automation and manual buids of the projects. Gradle Build Tool is easy to use and easy to integrate.

• load balancing of lots of user's for their software's accessibility.

Incentivized

• Gradle's methods to manipulate files is very flexible. It minimizes the amount of code one has to write to copy, move, or expand zip or tar files.
• Gradle uses Groovy, which is a Java like language. This allows for most computer engineers to come up to speed fairly quickly, for writing or maintaining gradle code.
• Gradle also supports DSL (Domain Specific Language), which is based on Groovy. The DSL language allows engineers to automate build jobs that otherwise could be very cumbersome to maintain or modify.

Incentivized

• Templates need to be more flexible with dealing with permissions.

Incentivized

• I'd like to see a way to specify how to run only certain tests in parallel, I tried this feature and for tests that involve interaction with SQL Databases sometimes I can't because of deadlocks.
• Not sure if there is something else, gradle has been working really good for us and they are adding improvements all the time which is awesome. I used to think the performance is a deal but the latest versions are addressing this issue very well

Incentivized

Gradle's language construct is good

Incentivized

I have tried to use Gradle for projects several times in the past, but there is just so much work in maintaining the build file that it quickly becomes untenable. I have been using Maven for many years, and even though the build file can be complex, it works without maintenance between releases.

Incentivized

Gradle has been an excellent tool for Android development. It has helped us create multiple versions of the app for different environments. It also takes care of all the packaging needs in the background without having to write all the code related to that. It is a no brainer to use Gradle with Android applications.

Incentivized

[Gradle is] a more modern version of open source build tools like Ant and Maven.
Whereas the build config was XML files which were tedious and error
prone, the modern DSL usage of Groovy to write these build files is a
great advancement. Also these config files can be inherited from top
level to each associated project.

Incentivized

• It had been very positive makes deployment faster with its Templates.

Incentivized

• In a distributed development environment, once we established a strong CI/CD model, Gradle proved to be a great choice to automate the various processes. Gradle also provides much flexibility, which is essential in today's development environment. The important benefit is that the CI/CD engineers can support development's needs quickly and reliably. This in turn supports faster testing and deployment, which generates higher ROI.

Incentivized