Alternate stratergy for WTSafeArea

[vijayaRath]

PTC recomnds using WTSafeArea for customization Manaement and Deployment . However , It has it's won challenges of maintaining the integrity and sgility . It make the system more human Dependent. I am looking for am=ny other alternating approach to manage and maintain customization with CICD implementation to automate the whole deployment process .

Please suggest

[avillanueva]

There are scripts for CPS patches that make use of this. Certainly custom resource bundles make use of aspects of this structure. I agree with you, its not the most ideal structure and I end up moving files from place to place to make use of this from my git repo. I know of a user who wraps all their code in a jar file that is just referenced by Windchill so nothing ends up in the codebase. That is the neatest approach I have seen.

[vijayaRath]

Thanks for QuickResponse . However , I am struggling to create a directory structure for my file management or  Git Repo . Can you please share more details on this and how we can achieve the near flexibility and consistency ?

[avillanueva]

Apologies about dropping off response here. Did you get a structure that worked? I struggle too here. Since most of what I was doing was Java coding, it made sense to have the root as the codebase. Then I started managing JSP files, conf files, resource bundles, etc. It got messy. For deployment, it was not as easy as putting files in their respective folder under the Windchill folder. I now think that having the Windchill folder (WT_HOME) be the root for your repo would make more sense. Compiled class files would be built to wtSafeArea and then pushed into main codebase. Seems like a bit to much hopping around. Again, I have not landed on perfect solution.

[vijayaRath]

I am being experimental and one of my approaches worked . However , I have excludes the JSPs and JS for now to Simplify . I will keep the forum  posted . 

Thank you so much for reverting .