2. How to optimize DevOps on IBM i?
The emergence of new DevOps-related terms reveals the level and extent of communication needed across all departments to progress the way business changes are managed. In DevSecOps, for example, security is enhanced by making it a shared responsibility and addressing it early in the application development process. Below we’ll examine how to achieve a single, common DevSecOps pipeline spanning all technologies, including IBM i. We will see how to automate an end-to-end DevSecOps cycle on IBM i – integrated with open source and cloud.
Integration with open source tools – CI/CT/CD pipeline
DevOps is helping organizations respond quickly to market changes, delivering better software updates to users faster. But moving to full DevOps can be challenging for IBM i teams faced with project deadlines, with little time to transition to a new full CI/CD model.
ARCAD helps you take the leap from traditional tools to a paradigm shift in DevOps and Modernization.
- Build an enterprise CI/CT/CD pipeline across all your technologies, integrating both vendor and open source tools. Open and modular, ARCAD solutions integrate with all standard DevOps tooling – GitLab, GitHub, BitBucket, Jenkins, Jira, CloudBees, Azure Pipelines and SonarQube to deliver a common DevSecOps pipeline across your entire enterprise and teams. You can also view a demonstration of a simplified CI/CD tool chain in our webinar “DevOps lite”: transition your IBM i development to CI/CD.
- Tune your DevOps pipeline to eliminate bottlenecks in your value stream. ARCAD’s unique metadata repository – a veritable knowledge base built from your own IBM i applications – powers the major Value Stream Management leaders of today –GitLab, HCL, TaskTop, Atlassian, … delivering unique insights into the agility of your DevSecOps flow on IBM i.
Read about the journey made by the Global Head of DevOps Tooling and Engineering Services at HSBC, helping to transition an ‘AS/400 development team’ into an Agile IBM i Pod with a fully automated CI/CT/CD DevOps pipeline in our article Transforming a traditional ‘green screen’ team into an Agile Pod for IBM i.
Achieving DevOps Maturity
When it comes to IBM i and the application development lifecycle, it would be easy to stick to the old ways of working. But in today’s world, those old ways just do not cut it. Forward thinking enterprises have massively adopted the Agile and DevOps philosophy. Source control is distributed and tools from the open-source world deliver changes continuously bringing new features to users faster. With all its differences – and its advantages – IBM i belongs in this open-source DevOps world too. However, how can you avoid being stuck in the past and adopt true DevOps on IBM i? Read our article DevOps maturity on IBM i: let go of the past.
Want to understand the key steps to full DevOps maturity and how to devise a roadmap that fits right with your teams? Watch our webinar DevSecOps maturity on IBM i – why is this important? to examine the emerging trends in DevSecOps and explore different routes to maturity.
Identify your level of maturity
All IT processes mature in stages so it’s important to recognize which stage you are at now in order to understand and plan for what’s next. If you rely on a mix of physical servers, inhouse data centers, and cloud technology, then to reach DevOps maturity you will need to standardize on tools able to manage such a hybrid environment. Similarly, if your application contains monolithic code then moving to a modern Web services/microservices architecture will require transformation of the code itself. Applications must be sufficiently modular to avoid slowing DevOps progress.
DevOps maturity models are used to assess the maturity level of DevOps within a company. There are several variations of the model but each one attempts to answer the same question – how mature is DevOps within the organization? To learn more about the different stages of maturity and what the obstacles to DevOps maturity might be, you can read our White papers DevOps Transformation: Engage your IBM i teams and Driving modern DevOps on IBM i.
To achieve this DevOps maturity, you will have two different approaches to choose from:
- The transformative route (fastest) – this route involves a complete plan which plots the fastest path to achieve and maintain mature DevOps on IBM i.
- The progressive route (tools driven) – this route is for organizations whose management believe that the transformative route may be too disruptive.
To avoid costly, high-risk migration projects in the future it is therefore important to act now and start
taking further steps on that IBM i DevOps maturity journey. Looking for tips to optimize your own DevOps implementation and leverage the competitive advantage of your IBM i? Take a look at our guide Modern IBM i DevOps: the “Lucky Seven” tips.