Jenkins vs. SUSE Linux Enterprise Server

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.

Incentivized

SLES has been the only OS for our large SAP landscape in North America and has been adopted by the rest of our global divisions because of our performance. We have not encountered any scenarios where SLES is not a good choice. We only use other OS when the vendor will not support SLES.

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

Incentivized

• Consistently performs well across various CPU architectures.
• It's very well supported both by the parent company, as well as SAP and other third-party companies.
• It is upgradeable across versions. We've performed upgrades from version 10 to 11 and from 11 to 12 without any major issues.

Incentivized

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

Incentivized

• The support window for service packs after a new SP is released is too short.
• Community engagement is low.
• There are times when supported packages fall too far behind and create compatibility issues with applications. The Open Build Service usually provides a way around this, though.

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

For the breadth of services, features and overall performance, I believe Suse Linux is a great choice for any enterprise. It still has to grow a bit in areas like online help forums and documents, but we are pretty much satisfied with our choice.

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

Support personnel are helpful and fairly fast to bring resolution to non-emergency issues. Patches are created and posted in a timely fashion. We so far have not had any major problems that needed support

Third party training was fast but mostly unnecessary as we were already Unix trained and Linux familiar

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

We went straight to SLES when we initially started migrating oracle to hana since at that time, HANA came on a pre-installed server that had to be purchased from an official vendor, and SLES was the only allowed OS. We stuck with SLES after we became certified to do our own installations because so far, SLES was a good fit for us.

Incentivized

We have successfully deployed on physical servers, VMs and in cloud all over the globe from templates of our own design

• 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

Incentivized

• Compared to others, use is more stable and scalable; easy to manage.
• The administration tools are very useful in helping the staff performance.
• SLES proved to be a very extendable product, supporting all of our infrastructure.
• The major reason I chose to use the product was the extensive enterprise peripheral support.

Incentivized