|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [JIRA] (JENKINS-13483) Hide snapshots created by... jfl...@accurev.com (JIRA)
- [JIRA] (JENKINS-13483) Hide snapshots creat... pjdar...@java.net (JIRA)
- [JIRA] (JENKINS-13483) Hide snapshots creat... jfl...@accurev.com (JIRA)
Ha, I hear you Peter. We are getting so many customer's that are using the plugin that we decided to put some more time investigating & helping out. You are right, a looping, show streams will take away resources from your accurev server & performance will suffer - especially when dealing with that many streams/snapshots.
One thing that has helped our customers steer clear of a full show streams is the new -r & -R flags. -r will give all of the parent streams of a workspace (or stream too). I'm not sure of the accurev version when that little nugget was introduced. It may be the 5.x series. There has been so much work put into update & populate that I'm pretty confident that a clean "refresh" of a workspace (update & pop) can go away and just utilize update.
I know you are concerned about compatibility issues but I think the new features/enhancements might be enough to draw a line in the sand & say if you upgrade accurev, you can get a new, optimized plugin. I know that there is a lot of old code "history" within that plugin and I would love to move past that - especially under the Jenkins fork.
I'm not a big java head but I can easily write code in perl if you want to try to interpret into java. Let's keep the ball rolling and see what we can come up with. Very happy to help.
--Jack