Hi,

For now we are using traditional way of migrating configuration changes using migration manager. However, do we have any option available in MAS where we can migrate the configurations using CI/CD? Any in-built tool for CI/CD?

Thanks,

Suhas

Hi Suhas,

there are plenty possibilities here: You can use pretty much any CICD tooling to deploy yaml definitions in OpenShift. There are some good tools build into OpenShift itself: https://docs.openshift.com/container-platform/4.12/cicd/index.html 

As for the Manage part: I would recommend putting as much as possible into dbc files. Using this approach You can automate the deployments of specific functionalities to Manage (for example with GitLab). 

Hi,

For now we are using traditional way of migrating configuration changes using migration manager. However, do we have any option available in MAS where we can migrate the configurations using CI/CD? Any in-built tool for CI/CD?

Thanks,

Suhas

I second using DBC files in a Maximo Customization Archive for deploying and maintain configurations. We have had success doing configuration in this way. 

We also use some of Sharptree's tooling to do deployments. It is pretty slick. https://marketplace.visualstudio.com/items?itemName=sharptree.maximo-script-deploy

Hi Suhas,

there are plenty possibilities here: You can use pretty much any CICD tooling to deploy yaml definitions in OpenShift. There are some good tools build into OpenShift itself: https://docs.openshift.com/container-platform/4.12/cicd/index.html 

As for the Manage part: I would recommend putting as much as possible into dbc files. Using this approach You can automate the deployments of specific functionalities to Manage (for example with GitLab). 

Hi,

For now we are using traditional way of migrating configuration changes using migration manager. However, do we have any option available in MAS where we can migrate the configurations using CI/CD? Any in-built tool for CI/CD?

Thanks,

Suhas

I would recommend this Manage CLI. https://github.com/nishi2go/masmanagedev-cli

You can use the masmanagedev-cli oc deploy to apply a new release of your customisations. Before that, you will have the daily CI/CD tasks to initiate your pipeline, download the latest code, run some tests if needed, and finally run the deploy command.

I second using DBC files in a Maximo Customization Archive for deploying and maintain configurations. We have had success doing configuration in this way. 

We also use some of Sharptree's tooling to do deployments. It is pretty slick. https://marketplace.visualstudio.com/items?itemName=sharptree.maximo-script-deploy

Hi Suhas,

there are plenty possibilities here: You can use pretty much any CICD tooling to deploy yaml definitions in OpenShift. There are some good tools build into OpenShift itself: https://docs.openshift.com/container-platform/4.12/cicd/index.html 

As for the Manage part: I would recommend putting as much as possible into dbc files. Using this approach You can automate the deployments of specific functionalities to Manage (for example with GitLab). 

Hi,

For now we are using traditional way of migrating configuration changes using migration manager. However, do we have any option available in MAS where we can migrate the configurations using CI/CD? Any in-built tool for CI/CD?

Thanks,

Suhas