Neewd Posted June 23, 2015 Report Share Posted June 23, 2015 Hey, My name is Clement and I am a french student from La Sorbonne and I make a study about SCM tools and for my master these I need some informations and feedback. So, With my colleagues and managers, we thought to criterias we need for our configuration management so I would like to know how your tools answer to that need and if possible with details (« we do that but … » or « we don’t do this especially but it’s possible to get around with this other functionality »)So here is the criteria with few words about what we think behind it. - Archiving of version Be able to archive the version when she’s not active anymore. - Release management Automation deployment in multiple servers, test before deployment… - Version management Be able to identify all the versions, the components in it. Be able to know where the version are deploy. - Change management - Branching - Global visualisation of the changes - Requirements tracking in the version Be able to attach some requirements to the version. - Dependencies between versions Be able to link versions with dependencies. If a version are not deploy, the deployment of the other version can’t be proceed. - Technological plurality Here is the fundamental point of my study. The big problem who bothers us in the SCM tool selection, is the Technological plurality. Indeed, we deal with JAVA, Mainframe, and possibly others languages in one software version. So how your tool deal with this ? If I'm not clear enough, I'd love to explain a little more my thought - Cost of the solution Thanks in advance to all The respondents. Regards, Link to comment Share on other sites More sharing options...
manu Posted June 23, 2015 Report Share Posted June 23, 2015 Hi! Hey,My name is Clement and I am a french student from La Sorbonne and I make a study about SCM tools and for my master these I need some informations and feedback.So, With my colleagues and managers, we thought to criterias we need for our configuration management so I would like to know how your tools answer to that need and if possible with details (« we do that but … » or « we don’t do this especially but it’s possible to get around with this other functionality »)So here is the criteria with few words about what we think behind it. Let's see if we can help you - Archiving of versionBe able to archive the version when she’s not active anymore. 100% Supported. https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide.shtml#Chapter10:Archivingrevisions - Release managementAutomation deployment in multiple servers, test before deployment… Plastic SCM works with multiple CI systems that are in charge of the testing and deployment steps. Tools such us TeamCity and Bamboo are the perfect partner for Plastic SCM. - Version managementBe able to identify all the versions, the components in it. Be able to know where the version are deploy. Plastic is changeset oriented, identifying the software delivered to a customer is extremely straightforward, each changeset is immutable, same happens for labels. More info here: https://www.plasticscm.com/documentation/user/plastic-scm-version-control-introduction-guide.shtml#Changesets - Change management This one is related with the previous one. Each check-in operation will generate a new changeset. I'll be happy to extend this if you need more info. - Global visualisation of the changes The best one you will ever find, the branch explorer. https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide.shtml#Chapter6:TheBranchExplorerView - Branching Branching and merging are the top 2 features of Plastic SCM. Extremely powerful and easy to use. - Requirements tracking in the version Be able to attach some requirements to the version. Plastic SCM supports a great number of Issue tracking systems. Atlassian Jira and FogBugZ are good examples. You can even visualize external task information inside the Branch explorer. You can also log check-in information inside the issue tracking system. Full info here: https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide.shtml - Global visualisation of the changes Plastic is a DVSC system but you can push the information to a central server so other developers can see your changes. You can even push the changes to another developer server, you choose. Plastic is very flexible, it can behave as a central VCS or a DVCS at the same time. Some other systems like Git can only behave as a DVCS and some other like SVN only as a centralized VCS. Plastic both - Dependencies between versionsBe able to link versions with dependencies. If a version are not deploy, the deployment of the other version can’t be proceed. Plastic provides the needed tools and operations to fetch info to handle a full ALM stack. Plastic covers the SCM area so other tools, like clarive for example, can complete it: http://clarive.com Link to comment Share on other sites More sharing options...
manu Posted June 23, 2015 Report Share Posted June 23, 2015 - Technological pluralityHere is the fundamental point of my study. The big problem who bothers us in the SCM tool selection, is the Technological plurality. Indeed, we deal with JAVA, Mainframe, and possibly others languages in one software version. So how your tool deal with this ? If I'm not clear enough, I'd love to explain a little more my thought As I said before Plastic covers the SCM area, deploying, testing, mainframe release etc is done in combination with Plastic SCM. "Jira - Plastic SCM - Clarive" is a good example of a full stack ALM chain. - Cost of the solution Pricing here https://www.plasticscm.com/pricing.html Best regards, Manu. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.