Jenkins vs. Snyk

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.

Incentivized

1) SAST Code Scan 2) Infra Code Scan 3) Docker Image Scan 4) SAS solution and provides good integration with various SCMS

Incentivized

• 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.

Incentivized

• Identify potential security issues.
• Analyse library dependencies.
• Secure code as it is written close to development.

Incentivized

• 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.

Incentivized

• Its a bit costly

Incentivized

While the day to day use is very easy, the configuration and setting up of the system or new projects can be cumbersome.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

Better Vulnerability research and GUI and usability

Incentivized

• 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.

Incentivized

• Nothing big on our specific projects.