I have tried using one deployment process for multiple software and I keep having issues with either the deployment process breaking, new software not being pulled in, or it only pulls in some of the software attached. I am swapping now to a single deployment process for each software (over 60 of them by the way) and the creation process is monotonous and could be so much faster.
If you going to recommend using single deployment processes for software. Allow us to create a preset deployment process - one that will apply the collections we want added and the duration of it. Would help speed up the time to create deployment processes for similar deployments and collections. Having multiple presets would be nice as I have a different patching schedule for software that goes to my servers.
This process needs to be faster.
| Product | Application Manager |
We are considering this functionality based on customer needs, but would recommend to create support tickets for the problems with using process with multiple applications.
We are also planning to provide application level settings that will help using same process for multiple applications.