Difference between revisions of "Directory:AccuRev"
(Created page with '<!-- MyWikiBiz users, note... Text that appears between these brackets are merely remarks. --> <!-- They do not appear in the actual page. --> <!-- The following is a simple Inf…') |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | < | + | '''AccuRev''' is a Software Configuration Management (SCM) solution developed by AccuRev, Inc. Founded by current CTO and architect Damon Poole in 1998, the company is based in Lexington, Massachusetts. The initial release of AccuRev 1.0 was made in 2002.<ref>http://www.accurev.com</ref><ref>http://www.masshightech.com/stories/2005/03/21/story4-2-million-round-revs-up-tool-developer-AccuRev.html</ref> |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | == Streams == | ||
| − | + | AccuRev does not use the concepts of branches or labels. Instead, AccuRev uses streams and snapshots. | |
| + | [[Source code]] files live in the streams and changes flow down through the hierarchy in which the streams are organized. Streams are first class objects that can be graphically visualized and manipulated by developers to change the behavior of the system. Content can be crosslinked from one stream to another enabling component-based development possible.<ref>http://www.theregister.co.uk/2007/06/04/accurev_streams/</ref> | ||
| + | * Dynamic streams are typically used to isolate project-level work effort | ||
| + | * Static (immutable) streams or Snapshots are often used to implement baselines for organization-level work | ||
| + | * Private Workspace streams are where the user makes their day-to-day actual changes. These changes are tracked by the AccuRev but are not visible to anyone else until the user chooses to promote the change to the workspace's parent stream. | ||
| − | + | == TimeSafe == | |
| − | + | AccuRev is designed around the TimeSafe principle which is the concept that a source control system must be able to unwind from the current state of the world and show users the exact state it was in at any point in the past in an effortless manner. AccuRev accomplishes this by ensuring that all operations are performed as atomic transactions with fine grained time tracking and global transaction numbers. Because files are not identified by path name, but by a global identity number, TimeSafe allows elements to undergo renaming refactoring without jeopardizing the history of the element.<ref>http://products.datamation.com/development/sd/1149533542.html</ref> | |
| + | == Change Packages == | ||
| − | + | AccuRev supports a method of managing changes as atomic units. By specifying the same issue number when promoting different changes, the changes will be grouped together into a single change package that can then be manipulate by issue number. Changes can then be moved through the stream hierarchies in an atomic manner - if any piece of the change package were to cause the promotion to fail, no part of the changes will be taken. This atomic nature keeps incomplete code sets from polluting a stream.<ref>http://www.computerweekly.com/Articles/2004/08/17/204554/AccRev-offers-alternative-to-file-based-SCM.htm</ref> | |
| − | |||
| − | + | == Comparing, Merging and Refactoring == | |
| − | + | The AccuRev user interface provides both a command line interface and a rich Java [[GUI]]. The command line interface also has options to output its data in XML format. | |
| − | + | Among the functionality provided in the interfaces are the ability to difference at many different levels - by files, by stream, or even by Change Package. Users may then elect to perform merges that consider not just the current state of the two elements in question, but with a tool that is aware of prior versions of the element and finds the last common ancestor to help simplify the job. | |
| − | + | The Version Browser is used to visualize the changes that files have undergone over time from the perspective of what streams and workspaces the file was modified by in a single screen. Additionally, the Annotatation Viewer allows users to see the last change made to each line of a file, when that change was made, who made it, and the transaction number that uniquely identifies the changes that were made at the same time. | |
| + | AccuRev supplies full support for moving, renaming and deleting files and directories while preserving their history. This frees developers to be able to conduct refactorings that rename elements without concern for losing vital information about the root of changes to the code they work on.<ref>http://www.agilejournal.com/resources/toolspotlight/2487-accurev-</ref> | ||
| − | + | == Architecture == | |
| − | + | AccuRev uses a client/server based architecture. Communication is performed via TCP/IP using an XML based protocol for actions, and streaming for file transfers.<ref>http://www.accurev.com/download/docs/4.9.0_books/AccuRev_4_9_TechNotes.pdf</ref> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | == References == | ||
| − | + | {{Reflist}} | |
| − | == | + | == External Links == |
| − | <div | + | [http://www.accurev.com] |
| − | + | <br> | |
| + | <div style="overflow:auto;height:1px;"> | ||
| + | [[Keyword:=AccuRev]] | ||
| + | [[Keyword:=SCM]] | ||
| + | [[Keyword:=Software Configuration Management]] | ||
| + | [[Keyword:=Streams]] | ||
| + | [[Keyword:=Damon Poole]] | ||
</div> | </div> | ||
| − | + | <br> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | < | ||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 21:36, 26 May 2011
AccuRev is a Software Configuration Management (SCM) solution developed by AccuRev, Inc. Founded by current CTO and architect Damon Poole in 1998, the company is based in Lexington, Massachusetts. The initial release of AccuRev 1.0 was made in 2002.[1][2]
Streams
AccuRev does not use the concepts of branches or labels. Instead, AccuRev uses streams and snapshots. Source code files live in the streams and changes flow down through the hierarchy in which the streams are organized. Streams are first class objects that can be graphically visualized and manipulated by developers to change the behavior of the system. Content can be crosslinked from one stream to another enabling component-based development possible.[3]
- Dynamic streams are typically used to isolate project-level work effort
- Static (immutable) streams or Snapshots are often used to implement baselines for organization-level work
- Private Workspace streams are where the user makes their day-to-day actual changes. These changes are tracked by the AccuRev but are not visible to anyone else until the user chooses to promote the change to the workspace's parent stream.
TimeSafe
AccuRev is designed around the TimeSafe principle which is the concept that a source control system must be able to unwind from the current state of the world and show users the exact state it was in at any point in the past in an effortless manner. AccuRev accomplishes this by ensuring that all operations are performed as atomic transactions with fine grained time tracking and global transaction numbers. Because files are not identified by path name, but by a global identity number, TimeSafe allows elements to undergo renaming refactoring without jeopardizing the history of the element.[4]
Change Packages
AccuRev supports a method of managing changes as atomic units. By specifying the same issue number when promoting different changes, the changes will be grouped together into a single change package that can then be manipulate by issue number. Changes can then be moved through the stream hierarchies in an atomic manner - if any piece of the change package were to cause the promotion to fail, no part of the changes will be taken. This atomic nature keeps incomplete code sets from polluting a stream.[5]
Comparing, Merging and Refactoring
The AccuRev user interface provides both a command line interface and a rich Java GUI. The command line interface also has options to output its data in XML format.
Among the functionality provided in the interfaces are the ability to difference at many different levels - by files, by stream, or even by Change Package. Users may then elect to perform merges that consider not just the current state of the two elements in question, but with a tool that is aware of prior versions of the element and finds the last common ancestor to help simplify the job.
The Version Browser is used to visualize the changes that files have undergone over time from the perspective of what streams and workspaces the file was modified by in a single screen. Additionally, the Annotatation Viewer allows users to see the last change made to each line of a file, when that change was made, who made it, and the transaction number that uniquely identifies the changes that were made at the same time. AccuRev supplies full support for moving, renaming and deleting files and directories while preserving their history. This frees developers to be able to conduct refactorings that rename elements without concern for losing vital information about the root of changes to the code they work on.[6]
Architecture
AccuRev uses a client/server based architecture. Communication is performed via TCP/IP using an XML based protocol for actions, and streaming for file transfers.[7]
References
- ^ http://www.accurev.com
- ^ http://www.masshightech.com/stories/2005/03/21/story4-2-million-round-revs-up-tool-developer-AccuRev.html
- ^ http://www.theregister.co.uk/2007/06/04/accurev_streams/
- ^ http://products.datamation.com/development/sd/1149533542.html
- ^ http://www.computerweekly.com/Articles/2004/08/17/204554/AccRev-offers-alternative-to-file-based-SCM.htm
- ^ http://www.agilejournal.com/resources/toolspotlight/2487-accurev-
- ^ http://www.accurev.com/download/docs/4.9.0_books/AccuRev_4_9_TechNotes.pdf
External Links
