I've used Ratiional ClearCase and ClearQuest in the past, but it's been a long time - at least seven years since I used CQ, and probably a decade since I used CC. On a project where we used both, I had them integrated. (I used them enough to refer to them collectively as "ClearWaste".)
I'm currently tasked with evaluating various CM-related suites for where I'm working now, and I'm finding it very confusing to determine just what IBM is currently offering.
I see ClearCase and ClearQuest are still sold. Are they actively supported?
As far as I can tell, DOORS and DOORSNg have replaced RequisitePro.
I see there's Jazz and Team Concert -- what's the difference between the two?
Does Team Concert use the other tools like ClearCase, ClearQuest, and DOORS? Does it replace them?
And finally, do the IBM tools still have a very cost compared to tools like the Atlassian Suite and Microsoft TFS?
I'm kind of limited in what I can see at IBM's web site since they use a great deal of YouTube videos and YouTube is blocked here. The only browser we have is IE and the IBM web sites to try demo version of the tools won't on IE, either.
I have a number of Linux shell scripts for automation of particular operations. For example: merging SVN revisions from one branch to other, update statuses of JIRA tickets, make an Oracle eBS build from sources stored in SVN or git etc.
I'm trying to use these automation scripts for different infrastuctures and customers. But I cannot share the script code for mentioned customers. Is it possible to put automation shell scripts in cloud and call these scripts from different infrastuctures? Are some available technical solutions how to call Linux shell scripts from cloud?
For example in cloud I could have shell function svn_merge() with parameters. But this script could be called from different infras with different parameters like "svn_merge <parameters>".
I will be happy to see any suggestions, any links to any free or commercial solutions.
Need your expter advice in setting up a new repository structure for our product development.
We have a software product, with 15-compnents and each of the 15-components have at least 15-modules.
Earlier our admin guy had configured the Stash server for us.
The current setup is like this:
Our IT engineer had created 15-Projects in stash/bitbucket server for 15-Components
For each of the 15-modules in a given component, a individual repository was created
Thus we have around 225 + 25(for additional module), totally 250 repositories to manage.
Individual developers creates their feature branches on their respective repositories and merge them to their production branch in their respective repo, after release.
Feature branches gets created only on a particular module in a particular repository which is getting affected for that feature.
If a developer is working on a feature, which is affecting 10-modules, this developer creates a branch in each of the repository which is affectting this module. Thus he creates 10-branches for a given feature in 10-different repositories.
In this way, we have many small teams working on many individual repositories corresponding to their module. Packages are made from each of the individual repository and delivered to our infra team, who deploys the product on our hosted servers.
Since source is spread all over the place, there is no baselines/tags created for this product. Also managing these many repositories by a single CM admin is too much to handle.
As a CM admin, I’m thinking of suggesting this structure for this product.
Create a single Project (Project A) in Stash
Create a single repository (Repo A ) in this project
Create a folder for each Component, i.e 15-Folders, under the repository root
(i.e Project A - /RepoA/Component1/Module1 Module2 ……Module15
/RepoA/Component2/Module1 Module2 ……Module15
/RepoA/Component3/Module1 Module2 ……Module15
/RepoA/Folder15/Module1 Module2 ……Module15)
In this way we’ll have single repository to handle and CM admin will create branches and developers will just make changes and commit their code.
Appreciate your response on these lines:
1. Is my suggestion to host a single repository for all the components correct?
is this achievable, what is your opinion on this repository structure?
2. We are developing a multi-tier, web application using PHP, Python, and Java Script. This application gets deployed on multiple servers. By using this single repository structure, do you see any issue or obstacle at a later stage on the line of development? What precautions should we take, if any?
3. Since the application is multi-tier, developers actually develop the application in the development environment (where multiple servers are setup to create a production sort of environment) using the shared work area in the environment, at times there are chances of one developer overwriting the others' changes.
What is your opinion on this kind of development?
4. Using this repository structure, how do we resolve the conflicts? Whenever a developer tries to push/pull the changes, he/she might face multiple conflicts not only from their changes. Should we call all developers to assemble at one desk and resolve the conflicts or is there any other better way?
5. We have many set of features getting developed on different branches. At times, many components are not modified in the some branches, still we just package them and release. What is your advice on this?
As CM admin, I see lots of advantages in managing branches and merges in a single repository structure. What do you suggest for our kind of development.
I have read many articles on web about the advantages/disadvantages of having single/multiple repositories. My Dev team is not conveienced with my approach. Thus I need answers to all my(actually their's) question in one place.
Would appreciate your detailed response for each of the above issues that we are facing. Your assistance in this regard will be very much appreciated.
I'd like to understand how companies using SVN, TFS, Git, GitHub perform backing out production deployments from two perspectives, your re-deployment method but more importantly, how are you indicating in your respective repo that if code was rolled back, what are you doing internally with your SCM tool to force a message to developers that code was backed out.
Hi, we are 100 memeber team working on one Java application. We are following Agile process and every week we will have a release for bug fixes and code changes.
Parallely we are also working on developement release on same code base.
Version Control tool is SVN.
For every week, (issues fix release and development release) all 50 devolpers are merging their changes manually. Becuase of this we have been facing many merge related issues and even some developers are missing to merge their code changes.we dont have any validation in place to validate developer word ( because of 300 + issues and 50 developers.) . we are simply assuming all developers merged their code changes as they mentioned. )
Kindly adivce any optimized solution or Merge Automations if any ?
This is regarding SVN branching strategy- What is harm in deleting trunk and copying branch to trunk to reflect production code which was delivered from Branch.
It is known that history on trunk will be lost however history on the repository still exist and any file at any revision can be recovered. So what would be issues with deleting trunk and recreating trunk from branch.