Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
why is the release management so slow?
René_Sartorio
Member, pcbaevp Posts: 58 PRO
FYI: @Axel_Kollmenter
3
Answers
Axel Kollmenter
I frequently need to release multiple drawings across various documents on Onshape. To speed up the process, I open up to five documents simultaneously and click on the 'Release' button in each tab. By the time I return to the first tab, it's usually finished loading, which significantly reduces my wait time.
Haven't experienced slow performance, but definitely feel we are due for some significant improvements. As we grow our implementation the entire Release Process just feel as an unfinished solution.
CAD Engineering Manager
@sebastian_glanznerwe know you would sent us an GIF. haha
Could it be that it gets slower the more configurations are present ?
Axel Kollmenter
Axel Kollmenter
having the same problem.
At the moment it feels like I spending almost 10-15 % percent of time waiting for workflow transitions and release updates. 😴
I'm not sure why each configuration needs to be individually released. I have to disable release management for all of my configurations except for the main one.
I don't know exactly how it works but I think every configuration you need to revision is basically duplicating each part it needs to load in the release management window, blowing up the load time.
@Jack_Brentano It's very hard to tell without looking at your project, but perhaps if you are not treating individual configurations as separate parts from a release management point of view, you can use the "exclude from properties" option on the configuration inputs? Then BOMs and RM will treat all configurations as a single thing (using the default configuration).