Likelihood to Recommend Control-M is a reliable and well-developed product with excellent vendor support that updates and expands the software often and offers a cloud-based deployment choice. When there are many
Batch processes in IT operations that need to be monitored and controlled to ensure IT services, Control-M is ideally suited for centralized workload automation and task management.
Read full review 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 Pros Control-M provides a single, centralized interface for monitoring and managing all batch processes in the organization. Nothing is hidden or left unattended in a timely manner. The proper use of the BIM component has allowed the change of paradigm in the operation, adopting a proactive management instead of the typical reactive management in the event of production failures. The use of Forecast and production simulations allows you to identify bottlenecks and focus first on managing those failures that have the greatest impact on production SLAs. Control-M/Change Manager has arrived to shorten development cycles from requirements gathering to production testing. It has been a utility that monetizes the development of Jobs meshes. The GUI is capable of efficiently handling more than 80,000 jobs per day. This is certainly a challenge in designing a good user experience. I don't know if there is a reasonable limit to this. One of my clients runs more than 80,000 Jobs daily and the GUI remains smooth all the time. Job-As-Code is a DevOps accelerator that has just begun to be adopted. Its implementation will make workload management even more cost-effective. Read full review 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 Cons As with most of the mainframe software products, documentation seems to be the weak link for the products - written by people and for people who already know what they need to do, not for people who are trying to figure how to use the product. We are a large JES3 mainframe shop. As with all vendors who still provide software for mainframe systems, software is generally designed and developed for JES2 and is frequently not fully tested in a JES3 environment before being shipped out. Read full review 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 Likelihood to Renew It is a great product plain and simple. We've had Control-M for 20+ years and the support that BMC Software provides is really second to none. There is always a situation that someone can think of where I have to say, "No we can't do that", however I'm confident that we've been able to meet and most of the time exceed our end user expectations with what the product can offer them.
Read full review Usability Control-M's overall usability is very good because it is simple to use. Control-M SelfService is an easy tool to give to some of the users who want to use a web interface. The training curve for most users is very short and most of the functions are very simple to figure out.
Read full review 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 Reliability and Availability We've had issues with a server crashing. The latest issue has the option for high availability which should help with that.
Read full review Performance I've never seen a performance issue with Control-M.
Read full review 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 Although the product is very stable there have been a few incidents when I needed support. I have worked with technicians from all around the globe because of the rolling support. This gives me the quickest support when I need it most in those early hours of the morning. The technicians I have worked with have been very knowledgeable and if necessary got help when needed.
Read full review 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 Implementation Rating It is a good approach to define a distributed architecture when you have multiple control-m servers.
Read full review Alternatives Considered We last reviewed the market in 2001 (schedulers are long-term commitments!) and Control-M edged (by a very narrow margin) the
Tivoli alternative, with
Dollar Universe (now part of Automic) back in third place. We also tested the Tidal Software scheduler (now part of Cisco) but I cannot see that listed here. Control-M won out through reliability and cross-platform support. Since we made our choice it has become clear that Control-M has moved ahead of the alternatives.
Read full review 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 Scalability Control-M doesn't really use that many resources
Read full review Return on Investment I would expect this product to give a positive return on investment. Running jobs in cron for example would require a lot more scripting effort to ensure that the proper notifications are done on failures. With the built in functionality in Control-M the effort would be greatly reduced Read full review 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 ScreenShots