Running an .INS file on an IFS Clou environment

Hi Théo.

You deploy an INS file on IFS Cloud environments using a delivery. The steps are:

1. Register on JIRA or similar tracking tool the task you want to perform with the INS file
2. The tool will provide you with an ID that you will use to generate the topic branch name for the INS file
3. Create the INS file, commit the changes and upload to the remote Git repository
4. Test the INS file using a topic environment and if everything is going well, merge to master branch
5. Run a Sanity build
6. Create a Delivery
7. Install the Delivery on the relevant environments

You can have a look at the following link in case you need to get more information about the Git workflow recommended by IFS to create modifications:

https://docs.ifs.com/techdocs/23r1/020_lifecycle/030_customer_solution_development/010_working_with_git/020_git_workflow_examples/git-workflow-cl/

You also need some knowlege on Cloud Build Place to run Sanity build and Delivery processes:

https://docs.ifs.com/techdocs/23r1/020_lifecycle/050_working_with_environments/020_sanity_build/

https://docs.ifs.com/techdocs/23r1/020_lifecycle/040_build_place_deliveries/010_ordering-deliveries/#1_delivery_creation_-_normal_delivery

Thank you much.

Best regards.

Gonzalo.

Hi @Gonzalo ,

thanks for these informations.
Where should the .INS file be placed in the branch?
Because we tested, and the file did not execute when starting the Build Place environment.

Thanks for your help!

Hi @TheoB

The location for this kind of files should be “<module>/source/<module>/database”. Here is an example for ORDER module taken from 23.1.0 Core code:

Thank you much.

Best regards.

Gonzalo.

Thank you for the reply. It is very useful for us.

but Did you modify the deploy.ini ?

Because How IFS know the name of the file to install , and in wich order  in case of several files to install ?  deploy.ini could be the solution

Hi @K4uFredeL 

I think the installer will pick the INS automatically and deploy it. There should be no need to use the deploy.ini file unless you need to specify some kind of dependency for the INS file. If I’m not wrong the delivery installer will deploy the files in “database” folder in the following order:

.CDB → .API → .APY → .INS

@TheoB, let us know if you’ve been able to run the .INS successfully.

Thank you much.

Best regards.

Gonzalo.