Likelihood to Recommend
It is really good when used along with Agile development. It can help control the dev/QA/staging environments and test the application easily without the code getting into a production environment. At the same time, if you only have small tasks, setting up Jenkins is a heavy task and too over-engineered. The user experience for simple tasks is not that great.
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 Used Jenkins as CI/CD tool. Extremely supportive community. Support connectivity with multiple clouds so the deployments over Azure, AWS, GCP, OCI and etc are supported. Trigger builds and deployments on Linux or Windows agents without issue. Support multiple version control tools. 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 User Interface: The Jenkins user interface can be complex and overwhelming for new users. Improving the user experience and making it more intuitive would help streamline the onboarding process and enhance usability for both beginners and experienced users. Configuration Management: Managing and configuring Jenkins can be challenging, especially when dealing with large and complex projects. Simplifying the configuration process and providing more user-friendly options for managing pipelines and jobs would be beneficial. Scalability: As projects grow and the number of builds and jobs increases, Jenkins can experience performance issues and scalability challenges. Optimizing Jenkins for larger-scale deployments and providing better support for distributed builds and parallelization would help address these limitations. 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/
/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 We run about 30 test projects through Jenkins every day, multiple times a day; this allows us to focus on new tests rather than manually running all these tests. We rely heavily on reporting capabilities and email notifications; we have some jobs that send emails every time they run so we know if there is an issue with any of our services. 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