ActiveBatch Workload Automation vs. Jenkins

Any large business or organisation that wants to manage their workload effectively and with the least amount of room for error might choose the ActiveBatch Automation tool. Being a consultant I feel that It aids in task automation and has the flexibility to change in response to varying company requirements. It helps to save huge time by doing all the repetitive tasks on daily basis. During the patching activity the schedulers can be stopped. It also help by alerting us if any system/job is down so that SLA can be saved. Overall ActiveBatch Automation stands as a dependable cornerstone for ensuring the seamless operation of our tasks.

Incentivized

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

• Businesses can use ActiveBatch to plan tasks based on parameters like frequency, dependencies, and the time of day. By automating typical actions like backups and data transfers, businesses can make sure that crucial operations go off without a hitch.
• Multiple systems and apps can be used in complicated workflows that ActiveBatch can automate. For instance, it can automate a workflow for processing orders from beginning to end, from the customer order through inventory control and delivery through the processing of invoices and payments.
• Files can be sent between many platforms and systems safely with ActiveBatch. Transfers to cloud-based storage systems like Amazon S3 and Microsoft Azure are also included in this. SFTP and FTP transfers are also included.

• 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

• On RARE occasions, have seen scheduling properties changed that don't take effect.
• Simpler to understand/more robust reporting options would be nice to have.
• Maybe I'm missing something, but why doesn't the Instances view show completion time? Just execution time and duration.

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

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.

Incentivized

We can easily add new plans/jobs in our batch schedules. Also, coordination with reporting and QA jobs is simple to do. Building schedules, restarting jobs, triggering dependencies is easy to understand. The system is very stable and allows us to easily see overall processing times.

Incentivized

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.

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

My colleague contacted them directly, I only know hearsay on this but it was not good.

Incentivized

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.

Incentivized

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.

Incentivized

The workload automation solution is based on the specific needs of an organization, as well as the features, capabilities, and costs of various solutions. A thorough evaluation process and consideration of these factors can help ensure the selection of a solution that aligns with overall business objectives and meets the specific needs of the organization.

Incentivized

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

• I have not run numbers to determine hard impact, but a quick estimate is that at least one job is running for a average of about 6 hours per day - that 6 hours, if done by hand, would equate to about 30 - 40 hours per day (and in some cases, could not be duplicated manually, as the job repeats faster than a person could accomplish one cycle.)

• 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