Hi,I do not know all details in the customization process, but why can’t you customize deploy.ini? There are lot of non-layered files that you are allowed to customize. It is too bad a bit messier to such a file since you need to do an overtake of the entire file. If there are changes in the file from RnD when taking an update, you need to re-do the customizations. However, there are tooling support to assist you in this.Note! I am no expert on customization, but I have not heard about any exceptions for the deploy.ini fileBRMats
Further updates This will never occur in a fresh install since it is caused by rebuilding views. In a fresh install we only add views I do find it very unlikely that it will happen in a clean build (i.e. the release build scenario) either since we turn of all conditional compilation in such builds. This error is happening when dynamic dependent view is rebuild, but when deploying all components we temporary turn of all dynamic parts in the views. This has happened a couple of times, but it must be an insignificant amount in the grand total. I believe that you do not need to take any pro-active action but be prepared to split the deliveries only if you run into this problem.
Hi,Sorry to say, but the client tool BAA, is not supporting any other version control system than Harvest. It is however possible to use svn, but then you need to manually setup and configure your environment. See if you can follow instructions here:https://wit.ifsworld.com/F1docs/Apps10/Foundation1/020_installation/500_references/050_build_automation/020_ifs_auto_builder/031_auto_build_dev_itd/default_extended.htmBRMats
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
