Combine multiple deploy packages into one
It would be nice to have the ability to select multiple packages in the deployment history, and clone all of them into one comprehensive deployment. This would help when there are multiple features moved at different times to a QA environment, but would like to move them all at once to Production.
Tara Wilkinson
shared this idea
-
Anonymous
commented
I agree this should be available in the Pro Tier. With cloning packages being available in the Pro Tier, it makes sense to make this available with it.
-
Anonymous
commented
This should be available in the Pro Tier. This is something that team with multiple people working would utilize daily.
-
Anonymous
commented
This should be available in the Pro tier!
-
Tim Savery
commented
Enterprise only? That's a bummer.
-
We've now released a beta of the combine multiple deployment packages feature in Gearset (note: this feature is only available on our Enterprise tier).
-
Adam Dry
commented
Yes please!!
-
Alex Searcy
commented
Yes, this would save so much time!
-
Gnanasekaran Thoppae
commented
This is a must have feature for a deployment tool like Gearset. It is often our need to deploy multiple times during a SIT or UAT phase but then once the exit criteria is met, we would like to combine many small deployments and make a single production deployment to avoid having to run all tests and longer downtime or go live time.
-
Shawn W
commented
Our org is composed of several smaller development teams all pushing changes through to production, so this feature would be a incredibly useful to our group!
-
Stephen K.
commented
This would be really helpful for our project!
-
Vanel
commented
Very helpful functionnality!!
-
Steven Rathbun commented
Same issue happening here. We deploy sprints on bi-weekly intervals. It would be nice to be able to combine those sprints (and defect fixes) into one package to deploy the theme to our SIT/UAT sandboxes.
-
Troy Hoshor
commented
100% this. We're dealing with this issue now in our environment. Iterative deployments to a staging environment means that you have to review by hand each deployment to combine them all into a single 'release' later on. It'd be amazing to check multiple and the combined metadata (applied to the current source environment) would be grouped up.