Likelihood to Recommend Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Read full review Initially you may think it’s not worth paying and that there are better free options, which is definitely a lie we once tried to live with. It has everything you may ever need in .NET world, code analysis and debugging works super well and all the SQL/noSQL related integrations are just next level compared to the competition. It’s worth every penny.
Read full review Pros Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration. Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues. Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection. Read full review Provides a smooth, efficient IDE for developing .NET applications. Performance has been much better than Visual Studio in my experience. Integrated refactoring tools are really comprehensive and useful. Integrates with other JetBrains products such as TeamCity, Upsource, dotTrace, etc. Read full review Cons The UI could be slightly better, it feels kind of like the 90s, but it works well. An easier way to filter jobs other than views on the dashboard. An easier way to read the console logs when tests do fail. Read full review Startup time. It takes a while to index big projects. Rarely it loses the intellisense and the only way to get it back is by restarting. Read full review Likelihood to Renew Due to the performance and productivity benefits we get with Rider, we will continue to use it for the foreseeable future.
Read full review Usability While the day to day use is very easy, the configuration and setting up of the system or new projects can be cumbersome.
Read full review Rider is a great IDE with extensive C# refactoring support and .NET-specific knowledge. This is great for building .NET applications but for our purposes, the Unity specific suggestions are really helpful.
JetBrains Rider is great as an editing and debugging environment. It reliably connects to the Unity editor and allows debugging, which some IDEs are not as reliable at doing.
Read full review Performance No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
Read full review Support Rating There is a large development community - but it is shifting as people move towards other tools. A lot of companies still use Jenkins and will build propriety tools, which doesn't help any of the open-source community. Jenkins has a lot of help and support online, but other, more modern, alternatives will have better support for newer tech.
Read full review The support forums and knowledge base are extensive and the JetBrains support staff respond quickly to new posts and help resolve issues. There is also a publicly accessible issue tracking system, which allows you to stay on top of any bug fixes or enhancement requests.
Read full review Alternatives Considered Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/
GitLab /Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
Read full review Rider is hands down smoother and way less glitchy than Visual Studio Enterprise. There are way more refactoring capabilities and spell check so that your code is readable, maintainable, and easy to follow. Since Rider is cross-platform, our developers are no longer constrained to only using Windows. We can now get a familiar development environment across Mac, Windows, or Linux!
Read full review Return on Investment Faster Time-to-Market: Jenkins automate the build, testing, and deployment process, enabling faster feedback and continuous improvement. Improved Quality: Jenkins automatically run unit tests and integration tests, ensuring that code changes meet the necessary quality standards. Cost Savings: Jenkins is an open-source tool that is free to use Read full review All people using the same IDE makes it much easier to ramp-up and collaborate Development and maintainment can be done in a more efficient way Read full review ScreenShots