Sorry, I was actually overly negative – and I’m definitely not trying to accuse you of anything, I’m really thankful for your response :happy: Just a bit frustrated, that’s all.
I think the issues I’m talking about are manageable if you have a localized team of developers, or a few local teams sitting in the same room.
Problems arise once you have several development teams on different locations, or when you have a high release load and have to test several releases at once. Doing parallel development on the same package, or even parallell releases on the same test server normally means doing one big development job, since all developers will affect each other when testing etc. – with no good way of keeping the code / releases separated.
It’s all or nothing: if you’re not testing one release at a time, then a difficult bug can clog up the whole release flow for a week or more, or require a full rollback/retest of several release candidates.
This is not a unique problem for webMethods specifically, but it’s much more pronounced.
I guess we have rather specific requirements: several highly independent development teams and as a result many environments that must be kept updated, and a tight production release schema on top of that (once a week or more often).
However, I think the points are still valid for “normal” projects as well. Automated tasks that are taken for granted in many languages today are entirely missing or poorly implemented, making the maintenance costs unreasonably high. At the end of the day, maintenance costs are much higher than development costs in almost any development project. The heated debates here on wmusers about whether to use java or flow for development actually doesn’t mean that much compared to the importance of release management, source management, built-in documentation and refactoring tools and other project infrastructure (the boring stuff, I know
Do you have any experience with some third-party tools that could help ease the pain? iTKO Lisa, Greenhat, Team Vista?