As large enterprises integrate the mainframe into their digital transformation plans, the question of how to transition to the new without disrupting what exists is a nagging dilemma. This question is critical especially when thinking about how to manage mainframe source code and its lifecycle without disruption. Check out our short video.
What is Working
Mainframe source code is traditionally managed by Source Code Management (SCM) tools like CA Endevor® Software Change Manager which provide Enterprise mainframe version control, build and lifecycle management of the source. SCM tools ensure effective controls and management of quality and reliability as the code is developed and pushed through test and production.
Transforming from what works on the mainframe to leveraging modern software development tooling like Git without disruption—this is the holy grail. There are disruptive approaches to starting over, each of which carries risks to the existing code lifecycle and auditability expectations. Why not then keep what is there and add Git integration? Let those that want to leverage Git’s experience and merge capabilities use Git and those that want to stick with ISPF continue without disruption.
For teams in enterprises, source code changes by multiple developers is inevitable. Integrating enterprise Git solutions like Atlassian Bitbucket best allows for the kind of parallel development teams are used to.
A developer can clone his repository, create the needed branches, and ready his workspace for changes quickly and easily. The developer can now operate on the mainframe source as he would any other language and save it to Git. From Git, he submits it to Bitbucket, where the team can resolve any change conflicts. From there, the developer or team merges the code into CA Endevor SCM, which completes the build. With a successful build the remainder of the CI/CD procedures continue.
The New Flow
Simply put, a developer, using whatever development environment they choose, can access mainframe sources, make updates, merge their changes with colleagues, and promote it to CA Endevor SCM .
CA Endevor SCM will build the executables, put them into test, run automated tests, update your project planning and change management tools while communicating through collaboration tools automatically.
The New Approach
What is cool is the freedom a developer now has to use their tools of choice. The Git and Git add-on features improve quality, productivity, and ultimately, the speed to market. Developers can collaborate on projects, work on different code releases in parallel, and make changes in the same source without risk. All this freedom in an approach that does not disrupt the mainframe procedures that are critical to the business.
Integrating Git and Endevor into your CI/CD pipeline is an important step in moving to DevOps. Tools like Zowe and CA Brightside allow you to access mainframe resources, automate procedures and integrate off host automation to drive mainframe procedures
Developers want freedom of choice. Large enterprises need controls. Leveraging the new integration of Git with CA Endevor SCM you can allow flexibility while controlling what matters.
Learn more about Git to Endevor in the following blogs or join our product validation process.