|
|
Case Studies in OpenMake Build Management Automation  An internal audit revealed that BNSF Railway needed to improve its build-to-release processes to meet audit requirements and help the company meet Sarbanes-Oxley compliance. The company chose OpenMake Software for enterprise build management, rolling it out to more than 200 users in 30 application teams, while also automating their development, build and release best practices. Their development environment included Microsoft and Eclipse. OpenMake’s build solution automated the team’s build processes, providing a complete audit trail of changes, progression and approvals through each lifecycle stage. Click here to view the BNSF Railway Case Study University of California - Los AngelesWhen the Regents of the University of California, Los Angeles campus reviewed the best way to standardize their build to release process, they chose OpenMake Software to do the job. Their challenge – standardizing the process of production readiness for 10 mission critical applications written by multiple teams using diverse languages including Microsoft Visual Studio, Microsoft Visual Studio .Net and Eclipse Java. Click here to download the Case Study. 
Fortis Bank incorporated Openmake into their IBM RAD development environment using CA SCM Distributed to automate the lifecycle process. Click here to view the Fortis Bank Case Study Fortune 500 Insurance CompanyA Fortune 500 insurance company uses OpenMake build solutions to streamline and manage their build-to-release process, resulting in more than two thousand production builds per month. Their applications are written in Java for the Linux platform. They have adopted an agile development methodology, which prevents the SCM team from having to be a middle man for builds and deploys. Developers have the ability to build and deploy their own applications in a secure and auditable way. This gives the company a competitive advantage by reducing the time to market for deliverables. A well-defined development / build / deploy role structure and workflow has been developed to ensure a standard, secure and auditable development to release process. Texas Based Financial CompanyA Fortune 200 insurance company uses OpenMake build solutions to gain competitive advantage by generating over six thousand production builds per month with only four build scripts, halving the number of shifts required of their build staff and saving nearly 200 man-hours per week. They are now deploying those people on to more strategic projects. They use OpenMake Meister in a mixed development environment that includes Java, Microsoft and z/OS platforms. They are moving to an agile development methodology and are using OpenMake’s dependency scanning capabilities for build avoidance and continuous integration builds. The CIO considers OpenMake technology strategic to their business because their customers are located around the world, and the majority of their interaction with the company is via the Internet. OpenMake gives them the ability to build reliable cross-platform applications with speed and agility. Midwest Grocery RetailerA Fortune 200 grocery retailer has standardized on OpenMake build solutions for their build to release process, helping them deliver organize and control their build process. Their SCM team can build applications created by their developers with minimal scripting and maintenance. They are using OpenMake to deploy Java applications as well as Unix C++ applications. This company has acquired other national grocery chains, and is bringing OpenMake into those development environments. To help meet their growing software development demands, they are expanding their development team globally by establishing a development center in India, where OpenMake will become their standard. Major Credit Card CompanyA major credit card provider has standardized on OpenMake build solutions to make certain that their builds are reusable, repeatable and auditable. Through an internal review of their development processes, they determined that their SCM lifecycle consistently failed audit even though they had a corporate-wide SCM tool. After adopting OpenMake, the Configuration Management Process was the only Process that passed their in-depth audit with flying colors because they used OpenMake Software to accurately match source code to production binaries. Auditing was so impressed, they sent a memo to the President applauding the team.
|
|
 |
LOGIN |
 |
CONTACT US |
|
RSS |
|
