Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
N/A
Micro Focus Diagnostics (discontinued)
Score 5.0 out of 10
N/A
Micro Focus Diagnostics was the analytics and issue diagnostics component of the Application Performance Management suite. It provided code-level visibility into transaction activity across applications and the network they are operating on. The product is no longer available for sale.
N/A
Pricing
Jenkins
Micro Focus Diagnostics (discontinued)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Jenkins
Micro Focus Diagnostics (discontinued)
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Jenkins
Micro Focus Diagnostics (discontinued)
Features
Jenkins
Micro Focus Diagnostics (discontinued)
Application Performance Management
Comparison of Application Performance Management features of Product A and Product B
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.
I would say on 90% of our agent installs everything works without any modification. If the application however makes a large use of memory based cache and analysis that classes will need to be excluded from instrumentation or it will impact performance.
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.
Agent level customization - For highly performant applications we can easily exclude instrumentation, yet still receive the benefit of historical tracking on common data points like CPU, Heap and GC cycles.
Support - In the 5+ years working with the product any HP solution engagements have been quick to provide a needed configuration solution.
Agent Diversity - Have used the product across 6+ differing middleware technologies comprising dozens of version (both middleware and java) combinations.
Agent installation - With its ability to support a silent type install, automating was a simple task.
The product does offer a lot of functionality - This can lead to a cluttered user interface and does take some time to become comfortable and proficient in its use.
Data Volume - We have had some issues in balancing the desire to keep all data and consuming infrastructure storage.
We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
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.
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
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.
While it has been several years since using BMC Patrol I like that HP doesn't require me to have a custom module added for every different type of product I would like to instrument.
