CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so they can accelerate innovation and growth.
$15
per month
Progress OpenEdge
Score 8.3 out of 10
N/A
Progress OpenEdge is an application development environment to keep businesses running, that enables users to leverage technology advancements to more quickly deliver business applications.
CircleCI is well suited if you, your developer, or team of developers have already worked with it in the past. They don't need to go through the learning curve of yet another Continuous Integration tool. Circle handles Continuous Integration workflows very well, including pretty complex workflows. With that said, Circle can get expensive if you need to run multiple containers in parallel and might not be as easy to setup as some alternatives, such as Jenkins.
Openedge is very well suited for financial based applications for 2 reasons. First, it has very powerful transaction scoping that will commit or back out of all changes in a transaction at once. This ensure that your data is "in sync." Second, it offers after imaging roll forward and replication for environments that require high availability or powerful disaster recovery in place.
Full customization and scripting abilities. Using tools like bash scripts, SSH, and Node, running almost anything upon committing some code to GitHub becomes possible.
Integration with all of our favorite services. GitHub and Slack in particular are crucial to our business and CircleCI's integration is seamless and full-featured.
Great config file syntax. Many CI services require you to perform advanced configuration in a UI. This is fine at first (and CircleCI offers this for many options available), but when you start needing to manage a large number of projects, committing configuration changes to a Git repository is more consistent and maintainable than making the change many different times manually in a UI.
Openedge databases are practically bulletproof, even when shot down abnormally. The offer complete transaction scoping, before imagining, and also after imaging for roll foward capability.
Openedge has a very powerful and easy to learn 4GL programming language that can be used in a traditional or object oriented manner.
Openedge also has powerful web services components, fully integrating both SOAP and RESTful web services.
Openedge is completely scaleable from 1 user to a fully distributed global enterprise solution.
CircleCI mostly getting built into both upstream platforms (Github/Gitlab) and downstream platforms (AWS, Azure, GCP), in which cases it's often a better fit or can be used as a part of existing tooling
UX can be confusing to navigate and see what's happening.
It's pretty snappy, even with using workflows with multiple steps and different docker images. I've seen builds take a long time if it's really involved, but from what I can tell, it's still at least on par if not faster than other build tools.
I haven't personally used their support service, but I have heard from others that they are responsive. I've also seen only one or two downtimes in over a year of use and both were no more than an hour or two.
Jenkins and Teamcity both have additional features that maybe you require, but they are also a lot more work to get set up and working. There's a much longer learning curve to getting these configured for a simple build. They're not hosted, so you have to maintain the infrastructure and scale yourself. They're both good products if you require more than CircleCI, but if not, skip the extra headache and go with something simple like CircleCI.
The decision to use openedge with our particular product was made such a long time ago that I certainly was not around to make the decision. And most of the other products that would have been compared at the time are likely no longer around. Which does speak to the longevity and benefits of this product. When you look back and see how long the same product has been going forward with constant improvements and remaining relevant without major disruptive changes, it is worthy of some credit.
