CCD versus other build/deploy processes

[MM_13610538]

I am using Windchill PDMLink Release 12.1 and Datecode with CPS 12.1.2.7

I have attended training for CCD for Windchill and have come to rely on it, and have even automated the CCD build, deploy, and Windchill restart.

We previously had a very chaotic manual process that moved Java classes around haphazardly.

A senior developer has claimed that CCD is not the way to deploy Windchill customizations (java, xml, etc).

Please respond with the PTC recommended best practice to manage Java and other customizations between environments on-prem.

Summary: If it was a choice between deploying .class files from a directory, or one .jar file from ant CCD deploy, what would be the best practice solution?

[avillanueva]

What did they recommend as the way to deploy customizations? As PTC moves more to cloud based deployments with Windchill+, their best practices are evolving but many customers employ similar types of pipelines to manage customizations and deployments. Certainly, manual is not BP. Recommend you chat up @jfelkins. There are also lots of threads on this topic here. 

[MM_13610538]

If it was a choice between deploying .class files from a directory, or one .jar file from ant CCD deploy, what would be the best practice solution?

[avillanueva]

What did your senior developer recommend? I've seen it both ways so not sure there is a best practice here. I can see how a one .jar file is easier since its easy to reference. If I was managing multiple instances at different versions or CSPs, this might be advantageous.  I have a simplier setup so I push class files to the wtSafeArea. Which ever makes your process more automated is the way I woudl go. If you have a solid build process, a .jar would be higher level.

[MM_13610538]

Not sure yet what he's going to recommend. 

I have CCD working end-to-end, fully automated from build to release, including pull requests, approval, and SAST scanning.  

The PTC training I took was 100% BAC and CCD.

In that training, I deployed every kind of customization with CCD packaging - Java, jsp, XML, softTypes, etc.  To me, it's a no-brainer.

[plmcore]

It is a better combination of ccd and BAC as ccd supports bac and Bac doesn't support all use cases

If you have good developer with Gadle / ant and  Windchill  knowledge, you can build your own build tool which can support incremental  and non incremental build and deployment capability and call it as part of your pipeline. This needs a person who understand windchill and pipeline so that he can easily integrate

We are used the ant tool as PTC creates ccd based on ant script and very powerful

Best Regards

plmcore

[Catalina]

Hi @MM_13610538,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution or please feel free to detail in a reply what has helped you and mark it as the Accepted Solution. It will help other members who may have the same question.

Of course, if you have more to share on your issue, please pursue the conversation.

Thanks,