We are a development team with around 11 developers and having only 10 bundles available on dev at a time is sometimes affect our work as there could be a lot going on, one can work on more than one ticket at a time. However, we don't need that much of the bundles on stage/production as those are running mostly latest 'main' branch's code. I am looking to see if is there any way we could increase the number of deployment bundles on dev environment? It would help to speed our work development work faster.
Kathy Tong
Thanks for everybody's interest in this idea. We have pushed Deployer 2.0 to all non-production environments (sandbox, staging, dev, outboundfeeds-sandbox - you may not have all of these non-prod environments in your organization).
This release includes both increase of on-deck bundles from 10 to 20 on non-prod environments as well as design system refresh with UX improvements.
Hi Kathy, Dan, Joseph, Pariscilla,
Thanks for the interest on this idea. It makes sense to increase the number of on-deck bundles on non-prod environments. It doesn't have any red flags in the first review, so we'll slot this for future consideration. I'll review, and prioritize this with the Engine team.
Ritchie, we definitely see the value on what you're describing and I see an implementation path for it. But it's definitely a cross-team discussion where delivery configuration may be the complex part of your comment. Can you submit it as a separate idea and I can bring it up in the next idea review session with the cross-team group and discuss the impact and effort of that idea?
For Arc team: If possible, could we also have like separate dev bundle URLs instead of a param? For instance, dev-01.pmn.arcpublishing.com would be for bundle #1, then dev-02.pmn.arcpublishing.com would be for bundle #2, and so on and so forth.
This would greatly improve our development process since we have more developers than slots available, impeding on our current workflow.
This would be wonderful! As our team has grown and has many new people have taken on important work in improving our readers' experiences with our product, we've run into a limit on the number of bundles we can test at one time. It would be great to have more slots available for testing so we can do more work. Thanks!
This would help our development process. Many times we have more than 10 tickets being worked on at one time, so being able to test those tickets on dev without having to coordinate with the other devs would be very helpful.