![\"IMB](\"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2021\/06\/iIlustration-devops-product.png\" "\\"DevOps")
<\/span><\/div>DevOps on IBM i (aka AS\/400 or AS400)<\/span>
\nWhy adopt it and how to get started?<\/h1><\/div>Wonder how to adopt enterprise-wide DevOps?
Learn to manage IBM i legacy apps with the same DevOps pipeline as distributed systems using tools like Git, Jenkins, and Jira for a secure future.<\/span><\/p>\n<\/div><\/div><\/div>- <\/i><\/span>1. DevOps: Features & Strategy<\/a><\/div><\/li>
- <\/i><\/span>2. How to optimize DevOps on IBM i?<\/a><\/div><\/li>
- <\/i><\/span>3. How to automate a continuous CI\/CT\/CD cycle on IBM i?<\/a><\/div><\/li>
- <\/i><\/span>\n4. Git, GitHub & open source tools<\/a>\n<\/div><\/li>
- <\/i><\/span>5. ARCAD’s DevOps tools<\/a><\/div><\/li>
- <\/i><\/span>\n6. Some use cases for ARCAD for DevOps<\/a>\n<\/div><\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
1. DevOps: Features & Strategy<\/h2><\/div>Why DevOps and how has it evolved?<\/h3><\/div>Application deployment is the most critical phases in the software development lifecycle. A decade ago, deployment was infrequent and a mostly manual and complex endeavor, scheduled at most monthly, quarterly, or even annually. Given the scale of change involved, software upgrades created contention between development and operations teams. At that time, development teams had already adopted mainstream agile methods and were releasing smaller software increments faster and more frequently, while operations \u2013 upholding their corporate constraints around application availability and compliance \u2013 became an apparent bottleneck in the process.<\/p>\n
DevOps has become a common practice in many organizations to respond more easily to these issues and more effectively to their business challenges. Today\u2019s digital transformation requires the time-to-market speeds that only DevOps can deliver. Organizations that have embraced DevOps either to the full or even partially can already testify that this approach brings a significant ROI.<\/p>\n
Today the question is no longer whether organizations should adopt DevOps, but how to implement it successfully and extend it enterprise-wide. The concept of Enterprise DevOps elevates DevOps into a business strategy, a process that adds value to the organization, not just IT.<\/p>\n
To learn more about evolution of DevOps, you can read our articles The evolution of DevOps<\/a> and Why DevOps? <\/a> or even download our White Paper Enterprise DevOps<\/a>.<\/p>\n<\/div>How does DevOps work?<\/h3><\/div>DevOps helps businesses respond rapidly to market changes, by delivering higher-quality software updates to users more quickly. It relies on continuous delivery and continuous test to reduce risk and obtain feedback fast and often.<\/p>\n
DevOps is an organizational change that depends on automated, tool-based collaboration between all actors in a software project: from developers, to testers, operations and end-users.<\/p>\n<\/div><\/div><\/div>
![\"Schema](\"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2021\/06\/Schema-devsecops.png\" "\\"Schema-devsecops\\"")
<\/span><\/div>An infinite feedback loop\u2026<\/strong><\/em><\/p>\n<\/div><\/div><\/div><\/div>- <\/i><\/span>Version control of all production artifacts<\/div><\/li>
- <\/i><\/span>\n
Develop and test against production-like systems<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Continuous Build, Integration, Test and Deploy<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Proactive monitoring of production environment<\/p>\n<\/div><\/li>
- <\/i><\/span>\n
Continuous improvement<\/p>\n<\/div><\/li><\/ul><\/div><\/div><\/div>
How to implement DevOps in your IBM i strategy?<\/h3><\/div>Digital transformation requires organizations to evolve very quickly in line with the needs of the business. The secret of DevOps is in its ability to deliver rapidly and without risk. Even today, in addition to new development, many organizations maintain legacy code on heritage platforms such as IBM i (aka iSeries, AS\/400) that are still critical to their business. To future-proof these applications, it is vital to modernize both the legacy code and <\/u>the development tooling used. By introducing agile methods and equipping teams with modern DevOps tools, it becomes easy to attract and retain young talent to safeguard applications into the future. Such organizations require a \u201cDevOps transformation\u201d.<\/p>\n
By applying DevOps methods in your IBM i development process today, you retain the competitive advantage of your custom IBM i applications, while integrating easily with new technology and tools. You gain reactivity and reliability and the ability to onboard new development talent with no prior experience on IBM i.<\/p>\n
Here are 5 key steps to ensure your DevOps transformation :<\/p>\n
\n- Define the target<\/li>\n
- Engage rapidly in \u201ctooling\u201d<\/li>\n
- Adopt a policy of \u201cquick wins\u201d<\/li>\n
- Communicate all-round<\/li>\n
- Make the upper management a stakeholder<\/li>\n<\/ul>\n
Discover these 5 tips in more detail in this article 5 keys to integrating IBM i into your DevOps strategy<\/a>. Learn more with our article Relevance of a DevOps strategy<\/a>.<\/a><\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>2. How to optimize DevOps on IBM i?<\/h2><\/div>The emergence of new DevOps<\/strong>-related terms reveals the level and extent of communication needed across all departments to progress the way business changes are managed. In DevSecOps<\/strong>, 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 \u2013 integrated with open source and cloud.<\/p>\n<\/div>Integration with open source tools – CI\/CT\/CD pipeline<\/h3><\/div>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.<\/p>\n<\/div>
![\"ARCAD](\"https:\/\/www.arcadsoftware.fr\/arcad\/wp-content\/uploads\/2021\/06\/schema-vs-Code-ibm-z-.png\" "\\"schema-vs-Code-ibm-z-\\"")
<\/span><\/div>ARCAD helps you take the leap from traditional tools to a paradigm shift in DevOps and Modernization.<\/p>\n
\n- 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 \u2013 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 \u201cDevOps lite\u201d: transition your IBM i development to CI\/CD<\/a>.<\/li>\n<\/ul>\n
\n- Tune your DevOps pipeline to eliminate bottlenecks in your value stream. ARCAD\u2019s unique metadata repository \u2013 a veritable knowledge base built from your own IBM i applications \u2013 powers the major Value Stream Management leaders of today \u2013GitLab, HCL, TaskTop, Atlassian, \u2026 delivering unique insights into the agility of your DevSecOps flow on IBM i.<\/li>\n<\/ul>\n
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 \u2018green screen\u2019 team into an Agile Pod for IBM i.<\/a><\/p>\n<\/div>Achieving DevOps Maturity<\/h3><\/div>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\u2019s 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 \u2013 and its advantages \u2013 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.<\/a><\/p>\nWant 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 \u2013 why is this important? <\/a>to examine the emerging trends in DevSecOps and explore different routes to maturity.<\/p>\n<\/div>Identify your level of maturity<\/h4><\/div>All IT processes mature in stages so it\u2019s important to recognize which stage you are at now in order to understand and plan for what\u2019s 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.<\/span><\/p>\nDevOps 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<\/a> and Driving modern DevOps on IBM i.<\/a><\/p>\nTo achieve this DevOps maturity, you will have two different approaches to choose from:<\/p>\n
\n- The transformative route (fastest) – this route involves a complete plan which plots the fastest path to achieve and maintain mature DevOps on IBM i.<\/li>\n
- The progressive route (tools driven) – this route is for organizations whose management believe that the transformative route may be too disruptive.<\/li>\n<\/ul>\n
To avoid costly, high-risk migration projects in the future it is therefore important to act now and start
\ntaking 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 \u201cLucky Seven\u201d tips.<\/a><\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>3. How to automate a continuous CI\/CT\/CD cycle on IBM i?<\/h2><\/div>Implementing a DevOps approach means deploying source code changes to production faster and more frequently. The “downside” of these frequent deliveries is the increased risk of a defect reaching production and a service disruption impacting the reliability of your organization. This is why successful DevOps implementations integrate test automation as part of the CI\/CD process.<\/p>\n<\/div>
\u201cCoding for the 21st Century\u201d doesn\u2019t mean just changing the way that you develop your user interface \u2013 \u201ctruly modern\u201d development means adapting to proven coding techniques and DevOps methodology to how you work with your applications. Learn with our webinar Truly Modern CI\/CT\/CD Development from Code to Deployment<\/a> how to break away from the being tied to 5250 and print file development by using modern RPG coding techniques.<\/p>\nIf you are testing manually, watch our Webinar Continuous Testing (CT) in your DevOps Strategy <\/a> to learn how to automate the process of Continuous Test, to catch errors as early as possible in the cycle.<\/p>\n<\/div><\/div>Automated testing & quality control<\/h3><\/div>Nowadays, It is vital that teams incorporate quality into all phases of software development and automate quality verification as far as possible to locate defects early in the process and avoid repeat effort. This is what is meant by \u201cContinuous Quality\u201d or CQ, which forms an essential safeguard \u2013 or quality gate \u2013 in the rapid delivery cycles in DevOps and CI\/CD workflows today.<\/p>\n<\/div><\/div><\/div>
![\"Code](\"https:\/\/www.arcadsoftware.com\/arcad\/wp-content\/uploads\/2021\/06\/picto-solution-code-quality-check-1.png\" "\\"Code")
<\/span><\/div><\/div><\/div><\/div>Automating the code analysis as early as the build or Continuous Integration phase means your team can find and fix systemic defects when the cost of remediation is at its lowest. How to achieve continuous quality? How important is Source Code Analysis (SCA) for DevOps? What are the limitations of functional tests? Read our article <\/span>Test Automation and Source Code Analysis for IBM i: why bother enforcing a new quality gate?<\/a>.<\/span><\/p>\nIf you want to ensure code quality and security on IBM i and before choosing the right tool you can start with the following questions:<\/p>\n
\n- How protected is your legacy and new code on IBM i?<\/li>\n
- Do your processes safeguard code quality and security, and meet your compliance goals?<\/li>\n
- Do you need to remove bottlenecks in peer review and give developers more time to develop?<\/li>\n
- Do you need to make code checking continuous?<\/li>\n
- Do you need to decrease the learning curve for new developers?<\/li>\n<\/ul>\n
Discover in our article DevSecOps \u2013 Automating Quality and Security in your IBM i source code<\/a> the solutions that our ARCAD CodeChecker tool can provide you or watch our Webinar Welcome to a New Year, Allow Arcad to enhance your development journey.<\/a><\/p>\n<\/div><\/div><\/div><\/div>Automate unit & regression tests<\/h3><\/div>Unit Test<\/h4><\/div>On modern, distributed systems, unit testing is arguably the most effective element of your testing strategy. A battery of well-designed unit tests \u201cforces\u201d the quality of your application as it is being developed \u2013 and ideally even before. Unit test assets are then re-used continuously right across the lifetime of the application to catch any regressions in the system.<\/span><\/p>\nYet how can unit testing benefit legacy applications on IBM i \u2013 and especially those that were not designed with \u201cunits\u201d in mind, and where monolithic code has been the norm? Unit testing is an indispensable and often missing link in software development on IBM i. Automated unit testing can make a DevSecOps pipeline on IBM i truly seamless – with measurable benefits in quality, speed and cost:<\/p>\n
\n- Auto-discovery of inputs and outputs to automate the creation of realistic\/useful tests<\/li>\n
- Integration of unit testing into the version control process<\/li>\n
- Auto-execution of tests as continuous part of the CI\/CD flow<\/li>\n
- Re-use of unit test assets for each program change<\/li>\n
- Dependency-driven maintenance\/update of unit tests<\/li>\n<\/ul>\n
Want to learn more about unit testing and how it can benefit existing applications on IBM i? Read our article Unit Testing: Beating technical debt.<\/a><\/p>\n<\/div>Regression Test<\/h4><\/div>To avoid the risk of regression and detect defects before they reach production, it is recommended to automate these regression tests for IBM i by recording the functional test cases and automatically replaying them with each application release.<\/p>\n
Watch our webinar Automated Testing: How to accelerate and protect your IBM i DevOps pipeline<\/a> to learn how to safeguard your IBM i application availability, with automated regression test:<\/p>\n\n- Record test scenarios using an easy-to-use emulator<\/li>\n
- Trigger the replay of test scenarios on each commit<\/li>\n
- Drive smart dependency-based test campaigns<\/li>\n
- Report on defects at their root cause<\/li>\n<\/ul>\n<\/div>
Test data<\/h4><\/div>Every IT organization does some kind of testing \u2013 whether it is unit testing by developers, QA testing by QA staff or full-on automated regression testing. In each of these techniques, one area that is largely underestimated is the role of test data. Yet how effectively this data is managed has a direct impact on the time spent in testing and the quality of the results. By reading our article <\/span>How to manage test data for smarter, faster testing?<\/a> you will understand why test data can be hard to manage, what are the best practices based on our experience and which tangible benefits you stand to gain from a consistent set of test data.<\/span><\/p>\n<\/div>Application deployment<\/h3><\/div>Application deployment is undeniably the most critical and high-risk phase in any application development cycle \u2013 directly impacting application availability and consequently the continuity of the business.<\/p>\n
IBM i apps and database upgrades in sync with distributed systems – on-premises, hybrid and multi-cloud – benefit from being deployed using release management tools to optimize continuous integration and delivery (CI\/CD) of IBM i software and data and to manage interdependencies from a single point of control.<\/p>\n<\/div>
<\/div><\/div><\/div><\/div><\/div>
Wonder how to adopt enterprise-wide DevOps? Application deployment is the most critical phases in the software development lifecycle. A decade ago, deployment was infrequent and a mostly manual and complex endeavor, scheduled at most monthly, quarterly, or even annually. Given the scale of change involved, software upgrades created contention between development and operations teams. At that time, development teams had already adopted mainstream agile methods and were releasing smaller software increments faster and more frequently, while operations \u2013 upholding their corporate constraints around application availability and compliance \u2013 became an apparent bottleneck in the process.<\/p>\n DevOps has become a common practice in many organizations to respond more easily to these issues and more effectively to their business challenges. Today\u2019s digital transformation requires the time-to-market speeds that only DevOps can deliver. Organizations that have embraced DevOps either to the full or even partially can already testify that this approach brings a significant ROI.<\/p>\n Today the question is no longer whether organizations should adopt DevOps, but how to implement it successfully and extend it enterprise-wide. The concept of Enterprise DevOps elevates DevOps into a business strategy, a process that adds value to the organization, not just IT.<\/p>\n To learn more about evolution of DevOps, you can read our articles The evolution of DevOps<\/a> and Why DevOps? <\/a> or even download our White Paper Enterprise DevOps<\/a>.<\/p>\n<\/div> DevOps helps businesses respond rapidly to market changes, by delivering higher-quality software updates to users more quickly. It relies on continuous delivery and continuous test to reduce risk and obtain feedback fast and often.<\/p>\n DevOps is an organizational change that depends on automated, tool-based collaboration between all actors in a software project: from developers, to testers, operations and end-users.<\/p>\n<\/div><\/div><\/div> An infinite feedback loop\u2026<\/strong><\/em><\/p>\n<\/div><\/div><\/div><\/div> Develop and test against production-like systems<\/p>\n<\/div><\/li> Continuous Build, Integration, Test and Deploy<\/p>\n<\/div><\/li> Proactive monitoring of production environment<\/p>\n<\/div><\/li> Continuous improvement<\/p>\n<\/div><\/li><\/ul><\/div><\/div><\/div> Digital transformation requires organizations to evolve very quickly in line with the needs of the business. The secret of DevOps is in its ability to deliver rapidly and without risk. Even today, in addition to new development, many organizations maintain legacy code on heritage platforms such as IBM i (aka iSeries, AS\/400) that are still critical to their business. To future-proof these applications, it is vital to modernize both the legacy code and <\/u>the development tooling used. By introducing agile methods and equipping teams with modern DevOps tools, it becomes easy to attract and retain young talent to safeguard applications into the future. Such organizations require a \u201cDevOps transformation\u201d.<\/p>\n By applying DevOps methods in your IBM i development process today, you retain the competitive advantage of your custom IBM i applications, while integrating easily with new technology and tools. You gain reactivity and reliability and the ability to onboard new development talent with no prior experience on IBM i.<\/p>\n Here are 5 key steps to ensure your DevOps transformation :<\/p>\n Discover these 5 tips in more detail in this article 5 keys to integrating IBM i into your DevOps strategy<\/a>. Learn more with our article Relevance of a DevOps strategy<\/a>.<\/a><\/p>\n<\/div><\/div><\/div><\/div> The emergence of new DevOps<\/strong>-related terms reveals the level and extent of communication needed across all departments to progress the way business changes are managed. In DevSecOps<\/strong>, 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 \u2013 integrated with open source and cloud.<\/p>\n<\/div> 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.<\/p>\n<\/div> ARCAD helps you take the leap from traditional tools to a paradigm shift in DevOps and Modernization.<\/p>\n 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 \u2018green screen\u2019 team into an Agile Pod for IBM i.<\/a><\/p>\n<\/div> 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\u2019s 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 \u2013 and its advantages \u2013 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.<\/a><\/p>\n 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 \u2013 why is this important? <\/a>to examine the emerging trends in DevSecOps and explore different routes to maturity.<\/p>\n<\/div> All IT processes mature in stages so it\u2019s important to recognize which stage you are at now in order to understand and plan for what\u2019s 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.<\/span><\/p>\n 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<\/a> and Driving modern DevOps on IBM i.<\/a><\/p>\n To achieve this DevOps maturity, you will have two different approaches to choose from:<\/p>\n To avoid costly, high-risk migration projects in the future it is therefore important to act now and start Implementing a DevOps approach means deploying source code changes to production faster and more frequently. The “downside” of these frequent deliveries is the increased risk of a defect reaching production and a service disruption impacting the reliability of your organization. This is why successful DevOps implementations integrate test automation as part of the CI\/CD process.<\/p>\n<\/div> \u201cCoding for the 21st Century\u201d doesn\u2019t mean just changing the way that you develop your user interface \u2013 \u201ctruly modern\u201d development means adapting to proven coding techniques and DevOps methodology to how you work with your applications. Learn with our webinar Truly Modern CI\/CT\/CD Development from Code to Deployment<\/a> how to break away from the being tied to 5250 and print file development by using modern RPG coding techniques.<\/p>\n If you are testing manually, watch our Webinar Continuous Testing (CT) in your DevOps Strategy <\/a> to learn how to automate the process of Continuous Test, to catch errors as early as possible in the cycle.<\/p>\n<\/div> Nowadays, It is vital that teams incorporate quality into all phases of software development and automate quality verification as far as possible to locate defects early in the process and avoid repeat effort. This is what is meant by \u201cContinuous Quality\u201d or CQ, which forms an essential safeguard \u2013 or quality gate \u2013 in the rapid delivery cycles in DevOps and CI\/CD workflows today.<\/p>\n<\/div><\/div><\/div> Automating the code analysis as early as the build or Continuous Integration phase means your team can find and fix systemic defects when the cost of remediation is at its lowest. How to achieve continuous quality? How important is Source Code Analysis (SCA) for DevOps? What are the limitations of functional tests? Read our article <\/span>Test Automation and Source Code Analysis for IBM i: why bother enforcing a new quality gate?<\/a>.<\/span><\/p>\n If you want to ensure code quality and security on IBM i and before choosing the right tool you can start with the following questions:<\/p>\n Discover in our article DevSecOps \u2013 Automating Quality and Security in your IBM i source code<\/a> the solutions that our ARCAD CodeChecker tool can provide you or watch our Webinar Welcome to a New Year, Allow Arcad to enhance your development journey.<\/a><\/p>\n<\/div><\/div><\/div><\/div> On modern, distributed systems, unit testing is arguably the most effective element of your testing strategy. A battery of well-designed unit tests \u201cforces\u201d the quality of your application as it is being developed \u2013 and ideally even before. Unit test assets are then re-used continuously right across the lifetime of the application to catch any regressions in the system.<\/span><\/p>\n Yet how can unit testing benefit legacy applications on IBM i \u2013 and especially those that were not designed with \u201cunits\u201d in mind, and where monolithic code has been the norm? Unit testing is an indispensable and often missing link in software development on IBM i. Automated unit testing can make a DevSecOps pipeline on IBM i truly seamless – with measurable benefits in quality, speed and cost:<\/p>\n Want to learn more about unit testing and how it can benefit existing applications on IBM i? Read our article Unit Testing: Beating technical debt.<\/a><\/p>\n<\/div> To avoid the risk of regression and detect defects before they reach production, it is recommended to automate these regression tests for IBM i by recording the functional test cases and automatically replaying them with each application release.<\/p>\n Watch our webinar Automated Testing: How to accelerate and protect your IBM i DevOps pipeline<\/a> to learn how to safeguard your IBM i application availability, with automated regression test:<\/p>\n Every IT organization does some kind of testing \u2013 whether it is unit testing by developers, QA testing by QA staff or full-on automated regression testing. In each of these techniques, one area that is largely underestimated is the role of test data. Yet how effectively this data is managed has a direct impact on the time spent in testing and the quality of the results. By reading our article <\/span>How to manage test data for smarter, faster testing?<\/a> you will understand why test data can be hard to manage, what are the best practices based on our experience and which tangible benefits you stand to gain from a consistent set of test data.<\/span><\/p>\n<\/div> Application deployment is undeniably the most critical and high-risk phase in any application development cycle \u2013 directly impacting application availability and consequently the continuity of the business.<\/p>\n IBM i apps and database upgrades in sync with distributed systems – on-premises, hybrid and multi-cloud – benefit from being deployed using release management tools to optimize continuous integration and delivery (CI\/CD) of IBM i software and data and to manage interdependencies from a single point of control.<\/p>\n<\/div>
Learn to manage IBM i legacy apps with the same DevOps pipeline as distributed systems using tools like Git, Jenkins, and Jira for a secure future.<\/span><\/p>\n<\/div><\/div><\/div>1. DevOps: Features & Strategy<\/h2><\/div>
Why DevOps and how has it evolved?<\/h3><\/div>
How does DevOps work?<\/h3><\/div>
<\/span><\/div>How to implement DevOps in your IBM i strategy?<\/h3><\/div>
\n
2. How to optimize DevOps on IBM i?<\/h2><\/div>
Integration with open source tools – CI\/CT\/CD pipeline<\/h3><\/div>
<\/span><\/div>\n
\n
Achieving DevOps Maturity<\/h3><\/div>
Identify your level of maturity<\/h4><\/div>
\n
\ntaking 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 \u201cLucky Seven\u201d tips.<\/a><\/p>\n<\/div>3. How to automate a continuous CI\/CT\/CD cycle on IBM i?<\/h2><\/div>
Automated testing & quality control<\/h3><\/div>
<\/span><\/div><\/div><\/div><\/div>\n
Automate unit & regression tests<\/h3><\/div>
Unit Test<\/h4><\/div>
\n
Regression Test<\/h4><\/div>
\n
Test data<\/h4><\/div>
Application deployment<\/h3><\/div>