App Connect

 View Only
  • 1.  Building a CI/CD Pipeline for ACE workload with CP4I

    Posted Mon December 21, 2020 02:50 PM
    Edited by Jess Leitsch Wed March 24, 2021 01:49 PM

    Running traditional IBM software in a Cloud Pak and OpenShift environment allows us to use modern DevOps practices to increase repeatability and reduce manual overhead. In this webcast, we will update the data processing logic of business data in App Connect Enterprise (ACE) and automatically deploy the new version using DevOps pipelines to the ACE Runtime environment running on OpenShift.

    Please join us in this on demand webinar, Building a CI/CD Pipeline for ACE workload with CP4I. 

    Share your questions below and you can watch the ondemand recording here. 



    ------------------------------
    Michael Buss
    Sign up for IBM Cloud Pak Demo Days Series : http://ibm.biz/CloudPakDemoDays
    ------------------------------


  • 2.  RE: Building a CI/CD Pipeline for ACE workload with CP4I

    IBM TechXchange Speaker
    Posted Tue March 30, 2021 01:27 PM

    Hi everyone, 
    You can watch the on demand recording here and download the slides here

    Please share any of your questions below. 

    Thanks, 
    Jess 



    ------------------------------
    Ulas Cubuk
    ------------------------------



  • 3.  RE: Building a CI/CD Pipeline for ACE workload with CP4I

    Posted Wed March 31, 2021 06:32 AM
    I hope you don't make too much marketing for this.
    I saw it a few times, that CI/CD chains slows down value creation.
    Instead of writing features or fixing bugs, the resources develop, fix and maintain the CI/CD Chain
    Some chains are not yet mature.




    ------------------------------
    Matthias Jungbauer
    ------------------------------



  • 4.  RE: Building a CI/CD Pipeline for ACE workload with CP4I

    Posted Thu April 01, 2021 07:11 AM
    Yes, it's certainly possible to go overboard in this area, and end up with a lot of people in a team becoming inwardly-focused! It's also true that organisations need to think hard about how far down the "Continuous Deployment" path they want to go, and whether they really need to push to production five times a day, as that level of automation does come with a setup and maintenance cost.

    What we've found internally, though, is that development staff became much more productive, and in fact it became possible to develop features that would never have seen the light of day without the agility the new techniques brought to the department. I should see if I can dig out some presentations and write up some of our experiences, as integration does bring challenges beyond the usual application development pipelines and our story might help others.