We are looking for a new source code control / config. management tool and I was curious if anyone had any input on the following possibilities:
I need it to manage source and other assets, build tools and other config management would be great but we could build those as needed.
The vast majority of our development is Progress OE using Architect/Studio but our application runs on a unix server so I would need to be able to retrieve code on the server, do builds, etc.
It would need to manage scripts/etc. used on the serve side.
We do a small amount of C# development using Visual Studio, so would like the tool to be able to handle our C# assets as well.
I've done a high-level look at the three above and all have some pros/cons, I was looking for any first-hand experience given the above needs. I'm also open to other thoughts, but the three above are on our radar beccause Git/TFS are already used in the company by other teams and Roundtable is so integrated with OE.
Any info appreciated.
andy
We have been using TFS for 3.5 years - currently with TFS Server 2012, integration with Eclipse (Architect / PDSOE on Windows and vanilla Eclipse on Linux) is fine.
Recently I've discovered the joys of Jenkins / PCT / Ant for continuous integration.
We are looking for a new source code control / config. management tool and I was curious if anyone had any input on the following possibilities:
I need it to manage source and other assets, build tools and other config management would be great but we could build those as needed.
The vast majority of our development is Progress OE using Architect/Studio but our application runs on a unix server so I would need to be able to retrieve code on the server, do builds, etc.
It would need to manage scripts/etc. used on the serve side.
We do a small amount of C# development using Visual Studio, so would like the tool to be able to handle our C# assets as well.
I've done a high-level look at the three above and all have some pros/cons, I was looking for any first-hand experience given the above needs. I'm also open to other thoughts, but the three above are on our radar beccause Git/TFS are already used in the company by other teams and Roundtable is so integrated with OE.
Any info appreciated.
andy
Flag this post as spam/abuse.
My 2 cents....
For pure integration with OE (code and DB) it is pretty hard to beat Roundtable. You would have to put a lot of work into parsing XREFs and making your own DB to reproduce all of the features available.
Pure source/object control is pretty easy and there are a lot of options out there. Getting that extra language/DB specific information is the hard part.
Note that the more an SCM does, the more likely it is that it is built around a particular assumption of a way of working. That can be a good thing if you like that way of working because it will reinforce your preferences. But, if you don't like it, it will be a bad match.
I can only second Jeff's comments on the usability of Roundtable - especially with OpenEdge development.
If you need to do OpenEdge application development, schema development and management as well as deployment, I doubt there are any other tools on the market that are more closely integrated with the OpenEdge stack.
This does require that the way in which you and your team works is compatible with the centralized SCM approach that RTB is built on. This is one of the features of Roundtable that a huge majority of the customers I have worked with over the years have seen as a key feature for achieving the control that they were looking for in an SCM tool.
In addition to the extensibility of Roundtable using the ABL, we have done quite a lot of work over the last few years to extend and automate Roundtable processes with the use of the standard APIs, our own extended ABL based APIs - and using Apache Ant Scripts and CI tools like Jenkins.
Together with the Roundtable development team we are looking at what we can do to make it easier to extend Roundtable with other tools and services out there. This includes things like integration with other tools that complement Roundtable like JIRA or other ticketing systems.