Hi All,
I have created a new custom component(module) in the Customer Solution Repository.
My plan is to commit all ACPs and also new MODs not related to Core components keep in this new custom component(module) and then deliver to Use Place environments via deliveries.
I have not seen any issues with this approach in previous Cloud versions as well (Say 22R1).
Does IFS have any formal recoomandations/any known issues in using a custom component(module) in 24R1 or we can continue on the same process we had earlier as well.
Page 1 / 1
That approach still works in 24R1 same as in earlier versions of IFS Cloud. You of course have to make sure to add the component to the "customComponents" section in the solutionset.yaml file and generate an appropriate deploy.ini file. For any modifications you have to make sure that you define the proper component dependencies to avoid deployment errors. See https://docs.ifs.com/techdocs/24r1/060_development/027_base_server_dev/007_concepts/150_deploy_ini/#connections
Thanks a lot
Yes, I do agree and it is done based on IFS documentation.
I assume there are no any known issues when it comes to Service Updates and Release Updates in 24R1 with a new component if we follow IFS ducumentation ?
I’m not aware of any issues.
The only issues I’ve seen is when the module dependencies aren’t registered correctly in the deploy.ini as that can cause issues on Release Update deliveries where all components are redeployed - but that is not limited to 24R1 and is then just based on an incorrect implementation.
Totally agree Jonas.
Many thanks :)
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.