Hi @RajaShankar
Recommendation would be to use cloud manager and discuss all your security reasons with AMS team and they will surely sort it out .
In case you want to leverage inhouse Jenkins for CI/CD build, it would be possible for all non prod environments but based on my experience with AMS, they won't prefer to do any builds on PROD environment except cloud manager. Deploying packages through CI/CD pipeline sometimes brings the entire instance down and AMS don't want to take the risk as it's a PROD environment. For PROD deployment, usually they would choose the deployed packages from Staging/Non prod environments which are the closet replica of PROD and where the codes changes are thoroughly tested.
Also, for the security reasons AMS won't share the PROD Publisher credentials as these credentials need to be setup on the Jenkins and in case person who has the access of Jenkins pipeline can easily get the credentials of PROD.
Talk to your AMS representative and surely they will provide you a solution. Hope this helps.