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.
Because of some of the best features the Control-M provides which includes but not limited to- Automation workload processing, manager file transfer, data pipelines, integrations, hybrid and multi cloud workflow.
We would still use Control-M as overall orchestrator to manage the workflows created in these other products. We do not consider them as a replacement for Control-M.
Control-M is very easy to use and it is easy to visually see how tasks are performing. Having the logs in one place when a task fails makes troubleshooting easier.
Control-M has proven to be much more reliable and not prone to crashes like UC4 had. It’s also more versatile since we can build almost anything we may need with the application integrator.
We have been using Control-M for almost 20 years and our teams are already trained to use it. Other tools are not as robust and resilient as Control-M. Control-M's graphical interface is very easy to use.
Control-M by far is the leader in this industry. The ease of use of the product and the ability to get others up to speed on using the product because of this is great.
Jenkins is highly customizable, making it ideal for complex pipelines that require scripting, conditional logic, and integration with a variety of tools.Jenkins offers thousands of plugins, giving it unmatched versatility.
Jenkins is highly customizable and flexible, supporting a wide range of plugins and integrations. Jenkins works with any version control system (Git, Subversion, etc.). Jenkins has a more mature ecosystem, and it may be better for large-scale, complex environments, especially …
One of the most important factors for selecting Jenkins would be the cost. Since Jenkins is opensource, there is a good amount saved from licensing and software procurement costs. Apart from cost, Jenkins is easy to understand and there is wide range of documentation and …
Bitbucket building was very slow, in order to improve that you have to upgrade to spend double or more minutes per build minute. The GUI was also very slow in updating on the progress of the builds, making things rather confusing. Gitlab worked a bit better in my opinion, but …
GitLab CI and Github Actions are other powerful options in the market also with a rising popularity and high interoperability with their respective platform. But Jenkins is still a good option for complex pipelines that require scripting and logic. Also, Jenkins uses as runtime …
I have used Spinnaker as a CD tool. Though it's a very powerful CD tool we still needed Jenkins for CI, so to save some hassle for us we opt Jenkins solely.
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 …
Both Jenkins and TeamCity do a good job of automating CI/CD. Jenkins runs much leaner than TeamCity - it only needs about a Gig of free memory, whereas TeamCity needs a fat 4 Gig free. Many tasks in Jenkins yml config can be very cumbersome, especially running local and …
Jenkins is easy to set up and supports a wide range of plugins. So any type of deployment is very easy. We can easily deploy Node, Angular, React, Java, Python, etc. Projects. We can also provide different credentials to different employees. So easy to track what is done by …
Team services, while very similar, did not really have that much more added features for the much higher price tag. The team has moved over to the subscription-based Visual Studio so we may be reevaluating this solution as now it is part of our subscription and no longer an …
Originally Jenkins was selected because it was the best around, but it has since been outclassed by more specific services or cloud-based services and tools that will do all of the heavy lifting for you. Jenkins still has a use case - but it's hard to argue the additional …
The big difference between Jenkins and other alternative tools is that Jenkins is open source and it’s free. Jenkins is very much about simple functionality. It’s a general CI tool that offers basic automation. It’s the most common CI tool on the market with a large community …
Scenarios where it's well suited are where you're running jobs across platforms. We have processes on our mainframe that have to complete our daily batch processing and the controlling handles the scheduling of the daily batch processing. Then once that's done, it moves into executing stuff on servers like SQL loads and transferring files to load into SQL and then also running reporting on the SQL servers when the data's been loaded and is available. It makes for a really smooth transition of the overnight processing the bank has to go through. That's our main function that we use it for currently. It handles it very well.
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.
Certificate on all levels: Each agent uses different keystrokes for different functions, such as AI, web service calls, and MFT.
It's really hard to manage these keystrokes.
Trust stores, in case control-m, act as servers; it should be simple to implement certificates from a corporate CA.
Some functions must be performed in the fat client, while others can only be performed through the web interface. This should be streamlined as soon as possible.
Jenkins can be vulnerable to security issues due to its open-source nature and the availability of many third-party plugins. There have been instances where malicious plugins have been discovered, and these can pose a significant risk to organisations.
Jenkins can require a significant amount of maintenance, particularly when dealing with plugin updates and compatibility issues. Maintaining a stable and up-to-date Jenkins instance can be a challenge for organisations with limited resources.
Jenkins' reporting capabilities are limited, and it can be challenging to extract meaningful insights from the data that Jenkins provides.
Control-M integrates with DevOps toolchains to automate the deployment of applications and updates. It supports Jobs-as-Code, allowing developers to define workflows programmatically, which accelerates development cycles and improves deployment consistency1.These use cases highlight how Control-M can streamline operations, enhance efficiency, and support critical business functions across various domains.
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.
Since it is GUI-based, it is not hard to use, although all new programs have a learning curve. The color scheme is easy to use to find the status of different Batch jobs. The check-in and check-out feature of job definitions is easy to use and avoids problems with users trying to use the same resource at the same time.
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.
He contactado varias veces con el soporte de BMC y ha sido bastante bueno, siempre han sabido darme una solución a lo que he pedido. Esta vez quiero hacer alguna nueva pregunta, pero no se si se me podrá contestar, ya que es algo que tal vez fuera de otro rango y no pertenezca a ellos.
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.
I met him as a Control-M consultant, performing migrations from CA to BMC. I knew the product and interface were not as friendly or intuitive as Control-M's and could not integrate new technologies and external applications. One of CA's excellent capabilities was the ability to incorporate executions with Java Scripting to obtain variable values or to order processes natively in the application using its utilities.
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.
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
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.
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.
