In the rapidly evolving world of technology and software development, change is the only constant. This has led to the widespread adoption of DevOps practices—principles aimed at streamlining software development and delivery. While DevOps is commonly associated with modern, cloud-native platforms, it is equally relevant to traditional environments like IBM i (formerly AS/400 or System i).

What is DevOps?

DevOps on IBM i refers to the application of DevOps principles, tools, and practices to the IBM i platform (formerly known as AS/400 or iSeries). In the past, deployments were scheduled monthly, quarterly, or even yearly due to manual processes, reinforcing the perception of IBM i as legacy infrastructure. However, DevOps aims to change this by shortening the development lifecycle and automating processes for more frequent, high-quality software deliveries.

The DevOps Process on IBM i

Here’s a typical sequence in the DevOps process for IBM i:

1. Change Request: A request for a new feature or bug fix is created.
2. Developer Assignment: The DevOps team assigns the request to a developer for analysis and action.
3.  Development: The developer implements the necessary changes.
4. Operations: The operations team sets up test data and the testing environment to ensure the application functions as expected.
5. Automated Deployment: The deployment process is automated to ensure a smooth transition to production.

The DevOps approach on IBM i speeds up the delivery cycle by automating traditionally manual processes, reducing the time needed to implement crucial updates.

Key DevOps Principles on IBM i

• Automation: Automating build, test, and deployment processes ensures consistency and reduces human error.
• Continuous Integration (CI): Regularly integrating code changes helps detect and fix issues earlier in the development cycle.
• Continuous Delivery (CD): Automating code deployments across environments allows for faster, more reliable releases.
• Version Control: Tools like Git are essential for managing code changes and fostering collaboration.
• Automated Testing: Automating tests helps catch bugs and regressions, ensuring code quality.
• DevOps Tooling: Tools like VS Code, Jenkins, Git, and Ansible are key components of a DevOps pipeline, streamlining the development and deployment process.
• Documentation: Maintaining thorough documentation of processes and configurations supports smooth deployments and future updates.

Getting Started with DevOps on IBM i

To embark on the DevOps journey with IBM i, follow these steps:

1. Assessment: Identify areas of your current processes and systems that need improvement or modernization.

2. Training: Ensure your IT staff is well-versed in both IBM i practices and modern DevOps methodologies.

3. Tool Selection: Choose DevOps-compatible tools such as Jenkins, Git, and Ansible for your IBM i environment.

4. Automate: Automate as many processes as possible, from building to testing and deploying.

5. Start Small: Begin by implementing DevOps practices in smaller projects to refine your processes before scaling.

6. Culture Shift: Encourage a culture of collaboration and continuous improvement across development and operations teams.

7. Monitor and Feedback: Continuously monitor production environments and use feedback to refine processes.

Note: One key difference between DevOps on IBM i and cloud-native platforms is that IBM i development is server-based. DevOps tools allow developers to work locally and then seamlessly push their changes to the IBM i server, which enhances collaborative development.

Benefits and Challenges of IBM i DevOps

Adopting DevOps on IBM i can yield transformative results:

Benefits:

• Faster Delivery: DevOps shortens development cycles, enabling faster time-to-market for features and applications.
• Improved Quality: Automated testing and continuous integration help ensure software quality by catching issues early.
• Better Collaboration: DevOps fosters collaboration between development, operations, and business teams, reducing silos.
• Scalability: IBM i’s scalability, combined with DevOps, allows businesses to efficiently respond to changing demands.

Challenges:

• Legacy Systems: Older applications running on IBM i may require refactoring to fit into a DevOps pipeline.
• Skill Gaps: Finding professionals with both IBM i and DevOps expertise can be a challenge.
• Cultural Resistance: Moving from traditional development models to DevOps can meet resistance, especially in established teams.