Boost Git Performance for IBM i
Optimize Git and Accelerate Development
Are you managing large Git repositories for IBM i applications? Or do you need to orchestrate smaller repos and concurrent testing and deployment? No matter which approach you take, Midrange Dynamics has solutions to boost Git performance for IBM i and ensure that your IBM i applications are agile, efficient, and scalable.
Git workflow in MDChange is specifically designed for IBM i, optimizing repository management, testing, and deployments for greater productivity, flexibility, and scalability. MDChange supercharges performance for GitHub, GitLab, Bitbucket, and Azure Repos, leading to great productivity gains.
Maximize Git Efficiency
for Large IBM i Applications
Git can be lightning-fast when dealing with just a few hundred items in a repository. But when dealing with tens of thousands of items — common for IBM i applications with substantial source code — transaction wait times can take minutes.
That’s where the Midrange Dynamics solutions come in. With MDChange, work efficiently with large repositories, or break them into smaller, more manageable ones. Either way, cloning is incredibly fast, and your Git experience is seamless and highly responsive.
If you choose to maintain a single large Git repository, MDChange has you covered. It automatically creates multiple clones directly on your IBM i system, using load balancing across several service jobs to ensure transaction wait times are minimal. This is true even for concurrent development on multiple branches.
Orchestrate Development Across
Multiple Git Repos
If you prefer to break your code into smaller Git repositories, MDChange orchestrates branch creation, handles merge requests, and manages dependencies across these repositories. This guarantees that your target environment will receive the necessary artifacts in the proper order. And once again, load balancing is employed to align processes across multiple service jobs for fast, efficient handling of all your Git repos.
Git Moving with MDChange
Seamless Git integration tailored for large IBM i applications ensures fast transactions, even for repos with tens of thousands of items.
Whether you choose to work with large repositories or break them into smaller ones, MDChange offers maximum efficiency.
MDChange uses load balancing across service jobs to minimize transaction wait times, even during high-volume development with multiple branches.
Automate branch-based libraries, IFS folder creation, data population, and continuous compilation, for fast concurrent testing—no matter the complexity.
Automatically track and deploy custom scripts, commands, and non-Git objects as you move between development, integration, and production environments.
Easily split deployment sets by features or other criteria, enabling targeted, time-sensitive deployments to multiple test or production partitions.
Agile Development Needs Automated Testing
Git excels for concurrent development, but agile development isn’t complete without the ability to test concurrently. While development cycles can span only a few days, testing can drag on for weeks.
That’s where MDChange takes things to the next level. When a feature branch is published automatically by MDChange or another process, MDChange instantly creates branch-based libraries and IFS folders using your custom naming patterns. It populates test environments, manages data, and continuously compiles changes, including dependencies that reside outside Git.
If issues arise, developers can modify the code directly on the IBM i. MDChange then tracks these changes and syncs them back to the repository, ensuring that everything stays up to date.
Seamless Retention of Custom Scripts and Objects
As your project evolves, retaining custom commands, scripts, and non-Git-based objects across environments becomes increasingly vital.
For example, when merging a feature branch into an integration branch, MDChange ensures that all custom objects and definitions from lower environments are automatically included in the deployment set for the target environment. It’s a seamless transition that keeps everything working harmoniously.
Simplified, Granular Deployments to Production
Whether the deployment set comes from a merge of several branches or a single feature branch, MDChange makes it easy to execute granular deployments to production. Split out specific sets based on features or other criteria. You can then send those deployment sets to various test or production partitions at designated times — giving you flexibility for targeted, time-sensitive deployments.