Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhat is the best alternative to Cake?
Top Pro
Top Con
Top Pro
Top Pro
Top Pro
Top Pro
Top Con
Top Pro
Top Pro
Top Pro
Top Con
Top Pro
Top Con
Top Con
Top Pro
Top Pro
Top Pro
Other build tools need wrapper modules to do certain tasks. The biggest disadvantage of these wrapper modules is that they bind you to a version of that tool. With Make you don't have that problem, there's no need for wrappers and no tools to bind you to a version, you can use any version of Make that you want. See More
Since Gradle uses Groovy instead of XML for it's configuration scripts, it achieves a great deal of flexibility but unfortunately that comes with slower builds when the project gets large enough. This is because the entire Groovy script has to be recompiled for every build instead of simply being parsed. See More
Since Gradle does not use XML but it uses it's own DSL based on Groovy, Gradle scripts tend to be shorter than other build tools that use XML. Boilerplate code is also considerably small because it's DSL is designed to solve a specific problem: moving the software through its lifecycle starting from compilation into static analysis and testing, packaging and finally deployment. See More
Gradle has full integration with Jetbrains IDEA. IDEA understands multi-module Gradle builds and automatically maintains the IDEA modules within the project. You also have the option to run unit tests with either the built-in JUnit/TestNG test runner, or delegate running the test to Gradle using the same visualization as the built-in runner. See More
The fact that it is based on Java does not hinder TeamCity's ability to support different build environments. TeamCity in fact supports a large number of languages and tools for each of those languages (build runners and test frameworks). Some of the languages/platforms that are supported include: Ruby, .NET, Java. See More
The user can easily compose dependencies between builds by adding snapshot and artifact dependencies, all on the one screen. All output of upstream builds is available to downstream builds. Triggering sets off the entire build chain and supports re-running of the portions of the chain that failed. See More
Requirement to explicitly name all inputs disqualifies Bazel for many workflows, e.g. those relying on tools that scan a directory tree themselves looking for files to process. Sandboxing as implemented in Bazel imposes further restrictions. If a command is successful when you type it in the shell, it should also be successful when pasted verbatim into a rule, but with Bazel it very often isn't. See More
Non-expert users can define parameters in a central interface, and Rudder will automatically make sure that IT services are installed, configured, running and in good health. All actions (checks, warnings, fixed errors…) are reported upon immediately in the user interface, keeping drift from nominal behaviour low. See More
Apart the agent on proprietary OS (AIX, Windows, ...) , Rudder is an open source and free software. This means that the code source is available on Github for every part of Rudder (Rudder webapp, and every other Normation repository). This also means that packages for a wide range of distributions are released and available to download freely. See More
Salt works around a Salt master which has multiple agents (Salt minions) that have a persistent connection to the master. Because of this persistent connection, commands to the master are fast to reach the minions. Furthermore, the minions also save various data to the cache in order to make execution faster. When compared against other tools to run the same actions, Salt almost always completes the actions in significantly less time. See More
AppVeyor's configuration (which is done from the .yaml file in the root of the project) is unfortunately very limited. The configuration is either tied to a branch or, in other cases, it's global. This limits the developer to a single build process. However, since you can use arbitrary scripts for building, all those limitations can be overcome. Configuration can also be done from the web UI without a .yaml file. See More
Well I suggest you check it out for yourself, but what I like most is that it's simple yet effective: no bells and whistles, simple black/grey/light-blue/white color scheme, it's immediately clear where you have to go for each specific task, and build settings pages are like that as well. Getting a 'standard' build running literally took me a minute the first time I used it. See More
While it's good that the gulp maintainers want the api to be as good as possible, it comes at the expense of stability. The upcoming gulp 4.0 release has another update to the way dependency management works which will require everyone to update their build scripts. It also makes it hard to look up information on best practices as the best practices keep changing, making a lot of the blog posts and questions about gulp out of date. See More
There are some features in Gulp which may not be very intuitive, or that otherwise should have been the default features instead of having to implement them through arguments. For example, to keep the correct folder structure when you are copying a file, you have to add {base: "lib/"} as an argument. See More
Since Gulp just uses streams at its core, you don't actually need a plugin wrapper to use a project that uses streams. If you use this approach, the you don't even have to worry about plugin maintenance at all, and get the bleeding edge updates as soon as they come out even if the plugin hasn't been updated. It also means if a project happens to not have a plugin, you don't need to write a new one, you can just use it as is. See More
In gulp, it's easy to pipe multiple steps together which you commonly need with build systems. For example, you may need to compile the javascript source files, then package them together, and then minify it. The streaming system makes this much easier. Additionally, it improves performance since all operations are done in memory (compared to I/O operations) and avoids the need of unnecessarily compiling files (compared to Grunt that has to compile all files even if just one has changed). See More
ReSharper has a built-in "go to implementation" feature which takes you to the body of the implementation of a method from an interface. This makes it easy to read code written by other people simply by going over the interfaces and using this feature to quickly find the implementation of a particular method. See More