Control-M from BMC is a platform for integrating, automating, and orchestrating application and data workflows in production across complex hybrid technology ecosystems. It provides deep operational capabilities, delivering speed, scale, security, and governance.
$29,000
per year
Jenkins
Score 8.3 out of 10
N/A
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.
Since IBM Workload Automation isn't compatible with all of our project's operating systems, we've decided to switch to using Control-C instead. Second, the provider provides top-notch customer service in the event of an emergency. Control-M is a lightweight program that places …
We've got scripts running on Linux, SQL jobs on window, cloud functions on AWs and god-knows what hiding in our prem stack and Control-M pulls it all together. Its perfect for multiplatform environments where job dependencies, timing and reliability are mission critical. Less ideal for small teams just running a few cron jobs, its just too powerful for that.
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.
Workload change manager is one of our favorite features of this product. It enforces standards, which is a huge benefit. Users don't just make crazy changes that cause issues with other jobs. It does great promotions from one environment to another, transforming all the data to match the next environment.
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.
I haven't come across too many spots where I'm not happy with the product. Most of the shortfalls were in my knowledge of the product as opposed to the actual product. Currently we're having a little bit of an issue with the deployment of the software to the servers, but it's more of an "us" problem than a product problem. I can't really give any good examples of shortfalls of the product that I've found so far.
It is one of the best solutions on the market, in terms of innovation, reliability and stability. Control-M provides security when used by the largest companies in Mexico such as banks, department stores and logistics. It has proven to be able to integrate with new technologies on the market and provide almost 100% availability, thanks to its automatic FailOver scheme.
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.
It has an excellent graphical user interface and robust functionalities, which any scheduling tool currently has in the current market. Strengthening security measures, such as role-based access control and encryption, is essential to protect sensitive data. Providing tools to optimize resource utilization and reduce costs would be valuable. Limited options for customizing the user interface can hinder productivity. Allowing users to tailor the interface to their needs would enhance the experience.
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.
Secondary Instances: Control-M supports the installation of a secondary instance of the entire Control-M environment, Control-M/EM, or Control-M/Server.Automatic & Manual Failover: In case of a failure on the primary host, Control-M can automatically failover to the secondary host if using Oracle or MSSQL databases. Manual failover is also an option, enabling a controlled switch during planned maintenance.Fallback: After resolving the issue on the primary host, you can easily fall back to it, or even designate the secondary host as the new primary. Database Replication: For high availability, Control-M leverages database replication from the primary site to a disaster recovery site. While replication is essential, its implementation and maintenance are the user's responsibility.
good page load times, efficient report completion, and minimal impact on integrated systems. Specifically, the well-designed GUI contributes to a positive user experience, and the platform's ability to automate various stages of the workflow, including Big Data processes, is highlighted as a key strength. Fast Page Loads: Control-M is reported to have a responsive user interface with fast page load times, allowing users to quickly navigate and manage their workflows
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.
Support is generally excellent. Getting lower priority ones resolved can take a while, but it's rare for something to have to be dumped in the "unfixable" bin. If you end up speaking to Houston or Tel Aviv, then you know you've got a "live one".
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.
Very knowledgeable instructors provide a hands-on, collaborative learning experience and can interact directly with instructors to develop our Control-M skills. This format allows for immediate feedback, in-depth discussions, and tailored guidance, leading to a deeper understanding of Control-M concepts and practical application. Face-to-face interaction fosters higher engagement and a more dynamic learning environment.
Simple and easy to use web based, well paced. Available any time. All online courses are simple and easy to access and use. Very practical everyday use scenarios and solutions. Incorporates software simulations, learning games, and built-in assessments to enhance comprehension and engagement. Online subscriptions are regularly updated with the latest product information, ensuring users have access to the most current knowledge.
As HA we have depend on the external DB, why don't we have HA feasibility with embedded DB. As with external DB, there are performance issues and fine tuning the DB. As if its embedded DB, Control-M it self take care of the functionality.
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.
Redwood RunMyJobs seemed impressive as well since it was also cross-platform, flexible, and versatile. However, we went with Control-M because it was less expensive and we were already using it on our mainframe environment. The distributed version of Control-M was much more user-friendly due to the GUI instead of the command-line interface used on the mainframe.
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 Control-M offers flexibility with usage-based and subscription-based pricing, some users might prefer more predictable, upfront costs, especially for large-scale deployments. A potential area for improvement could be offering more options for fixed-term contracts with predictable pricing based on factors like the number of agents or jobs, providing a clearer budget for long-term planning
awesome product.Control-M delivers advanced operational capabilities easily consumed by Dev, Ops, data teams, and lines of business.Control-M Workflow InsightsApplication and data workflow observability: Increased confidence that SLAs are being met for Control-M users and IT leadersComprehensive control and management capabilities: Enhanced dashboards and reporting with constant telemetry and intelligent analysis on executing workflowsSelf-service visibility: In-depth reporting to help teams work autonomously
Strengths: The vendor provided strong post-sales support, timely issue resolution, and effective onboarding. Their technical team was knowledgeable and responsive, ensuring smooth integration and minimal disruption. Training resources and documentation were comprehensive. Areas for Improvement: While overall service was excellent, occasional delays in advanced customization or escalations slightly impacted timelines. More proactive optimization suggestions could further enhance value.
Control-M has improved service delivery times, reliability and quality of batch processing.
It has simplified the management of the operation and the use of the alert system has made it possible to act in a coordinated and efficient manner to solve problems.
The implementation of policies has made it possible to make greater use of Control-M and thus reduce development costs that are generated unnecessarily when the potential of the system is not considered.
