Similar information can be obtained for the history of other SCM elements like components and streams in addition you can explore baseline history of them. Most of the options in this menu are also available in history contexts navigating in a similar way as we have done for a file in this post.
I will try to write a bit about them in the future …. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account.
Notify me of new comments via email. Notify me of new posts via email. Following the previous scenario and using the Money That Matters sample, you could get something like the following click image to enlarge : Each entry in this history view represents a change set in which the file was modified in the current workspace. Moreover, there is a bunch of actions you can perform for the change sets that appear in this view with simply a right click operation note not all that appear work for a change set context : History of the source file in other contexts: Now back to the scenario, in parallel development there are potentially more changes in the source file from the ones you have in your repository workspace.
But the above APIs provide huge content as response. Maybe there is a better way to get the information required? Hi Mr Richard, Sorry for the late approval. Maybe indeed there is a better way to get the snapshot and baseline information. But if it works, it works. And the number of snapshots I am dealing with is small enough to not bother too much about it. Thank you for your pointers. Our team is considering migrating to git as well. Can you please share your script? Unfortunately, I did not get company permission to share the scripts, so you have to do with the snippets in the article.
If you have specific questions, feel free to ask. I am currently working on the article on the Git import, but it is progressing quite slowly. You are commenting using your WordPress.
You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. This site uses Akismet to reduce spam. Learn how your comment data is processed.
I have over 30 years experience in Skip to content. Home About. Session self. Share this: Twitter Facebook. Like this: Like Loading I have over 30 years experience in software development in the technology industry, with the last 15 years mainly in process improvement, deployment and integration of methods and tools in the area of Agile SAFe, Scrum , CM and ALM.
I am strongly interested in the complexities of collaboration and integration in multi-project and multi-site organizations. It supports geographically distributed teams and has strong support for parallel and agile development. It is built from the ground up to support a highly-integrated collaborative development environment, integration with defect tracking, integration with builds, and process-centric automation. With these other software engineering aspects in mind, the source control component is flexible to accommodate different programming practices, such as component-driven development or feature-driven development.
The unit of change in RTC source control is the change set, which provides atomic changes to a set of files and folders. Change sets are the base currency and can be shared through streams and work items. Instead of combining all of your change sets in the same namespace, components provide an additional composition mechanism to organize work in the same repository.
Files are grouped into change sets which belong to a specific component, and components are grouped into streams. Rational Team Concert source control was designed for development across multiple streams or branches. Teams or projects own a set of streams that provide a simple mechanism for sharing change sets between team members. Keyword expansion mess-up merges and makes conflict resolution hard.
But I know people like having that little tag at the bottom of an html page. The alternative is to add the keywords and have a build step eg, some ant script which calculates the substitution. I don't know all the possible keywords for substitution in cvs and cmvc I would expect to be able to customize the substitution in my build definition, with published suggestions for CMVC and CVS.
That way I can make versionid be any combination of available properties. Just provide the list of available properties and let the users pick.. Just document them like in " Getting Started with setting up Jazz Builds ".
I guess what I'm saying is don't delay the item because we can't provide all the mappings. If something doesn't map, we could map it to something else or to blank. We have a command line and ant task that may be able to help you out, we use this to help decide if we should increase version qualifiers, it's called " lastMod ".
It basically checks the diff between two baselines and returns the timestamp of the latest change. If there are no changes, the timestamp won't change.
0コメント