161 results about "Revision control system" patented technology

A method for deploying source code from a version control system to at least one of a web server and an application server is provided. The method uses a build environment configured to be coupled to a client utility and a version control repository. The method includes scheduling a build request using a build scheduler, prompting a deployer to invoke the client utility including designating a specific time for execution, extracting source code at the scheduled time from the version control repository using the build environment, verifying promotion groups, building compiled modules to form an application, and deploying the application to at least one of a web server and an application server.

A version control system for managing versioned files comprises a central server storing a repository of the versioned files. At least one proxy is connected to the central server. Each proxy includes a read-only cache for storing data from the repository. At least one client is connected to each of the proxies. Modifications to the versioned files may only be made by the central server.

Methods, systems, and computer program products may provide pre-merge conflict avoidance in a revision-control system. A pre-merge conflict avoidance method may include identifying by a computer system a portion of interest of a revision-controlled base source code stored in a source-code repository, the base source code being developed by a plurality of developers. The computer system may determine whether at least one of the plurality of developers has made a change to a portion of a first copy of the base source code corresponding to the portion of interest prior to commitment of the first copy of the base source code to the source-code repository. In response to a determination that the at least one developer has made a change to the portion of interest, a notification may be produced about the change to the portion of interest by the at least one developer.

A system and methods for versioning software components in connection with a computer programming language are provided. In exemplary aspects, the versioning system makes use of intelligent defaults, provides a vehicle for unambiguous specification of developer intent and implements conflict resolution rules in connection with the versioning of software components. In another aspect, the versioning system bounds names at run-time, but does not bound offsets at compile-time.

A repository manager facilitates robust revision control of components of a large scale system. The repository manager stores system components under revision control in a repository, according to internal names. The repository manager also stores binding information between internal names of system components and associated external names, as well as component attribute information. The repository manager provides users with working areas, from which they are able to access system components according to their external names, via the repository manager. As users perform operations affecting system components, the repository manager keeps track of the performed operations. Responsive to a user committing a set of changes, the repository manager updates the master repository according to the performed operations, associates a new version number with the resulting state of the repository and synchronizes the user's working area with the updated repository.

A computer implemented method and computer usable program product for version control of source code. In one embodiment, a source code file is scanned for relationships between source code sections. A semantic graph with dependencies and metadata describing the source code sections is constructed. The dependencies indicate the relationships between the source code sections. If changes are received for the semantic graph, the semantic graph is modified with the changes to form a modified semantic graph.

A method of data control for a system server and a sub-network including a plurality of user terminals, the method comprising the steps of providing the system server with updated software versions, selecting one of the user terminals, requesting from the system server a list of the updated software versions that are absent in the selected user terminal, determining whether the unselected user terminals include any of the absent updated software versions, receiving the absent updated software versions to have been included in the unselected user terminals, receiving the absent updated software versions to have not been included in the unselected user terminals, and upgrading the selected user terminal with the received absent updated software versions.

The present invention teaches a methodology for provisioning and managing a network having many network devices. In certain embodiments, groups of member devices are created each having a group policy configuration inherited by member devices. A variety of rules regarding prioritization, versioning, system snapshot, redo and undo are also taught. This embodiment is useful when the network devices can be partitioned into groups of similar type devices for similar applications. Similar physical attributes can also be mappend into identical virtual attributes, enabling policy configurations to be applied to varying devices and physical attribute configurations can be resolved upon device installation.

The present disclosure relates generally to a data integration system that integrate an object based data integration tool, such a GUI-based data integration tools, with version control systems using a relational database repository for persistence. Examples of distributed version control systems include Git, Mercurial, and Bazaar, and examples of centralized version control systems include Subversion, CVS etc. in centralized or distributed environments.

An inventive system and method for versioning relational database disjoint records comprises a relational database, configuration files translated into query files, and a version control system, wherein each query file is stored and checked into the version control system, updating a version number of the query file. Each query file comprises a set of query statements. Query files are retrieved from the version control system based on the version number or an independent data item, and put into the database for analysis. In one embodiment, one of the configuration files comprises a configuration of a device, such as a router, a switch, a firewall, or a medical record. The method comprises acquiring configuration files, changing the configuration files into query files and storing the query files, and checking each query file into a version control system, wherein the checking in updates a version number of the query file.

Some large software development projects need more than one versioning system to accommodate not only a diversity of document formats and data types, but also the geographic diversity of its programmers. However, having more than one versioning systems is generally very expensive. A major factor in this expense is the requirement for a separate application program interface (API) for each separate versioning system. Accordingly, the inventors devised an exemplary API architecture which can be extended with “plug-in” protocol providers to include virtually any number of separate version stores or versioning systems. The exemplary architecture includes a generic command parser and a command dispatcher. The command dispatcher operatively couples to one or more protocol providers, each coupled to at least one version store. Inclusion of the OLE DB-compliant interface and the command parser in the exemplary embodiment saves the protocol providers the effort and expense of replicating these features, thereby reducing the cost of adding version stores.

A software-development system or versioning system has a collection of modules for performing individual development functions such as document editing, keyword processing, and private-copy management. Each module has an interface compatible with that of the others, so that modules can be added to or substituted for the original modules, if the new modules conform to the interface. The architecture of this system supports the performance of development actions such as document merging and keyword expansion at any location within the system. The system operates upon documents and files as objects in an object space, rather than in name spaces.

The present disclosure relates generally to a data integration system that integrate an object based data integration tool, such a GUI-based data integration tools, with version control systems using a relational database repository for persistence. Examples of distributed version control systems include Git, Mercurial, and Bazaar, and examples of centralized version control systems include Subversion, CVS etc. in centralized or distributed environments.

This disclosure relates to database systems and, more particularly, to database systems with version controlled data. A version controlled database program resides on a computer readable medium, having a plurality of instructions stored thereon, which, when executed by a processor, cause the processor to perform operations. The operations include defining a version object software layer. The version object software layer may be configured to read and write data of a version controlled database to a physical storage medium, maintain one or more versions of at least one element of the data, and provide access to the data. The operations may also include defining a database management software layer. The database management software layer may be configured to read and write data to the version object software layer and provide a database access interface for accessing the data.

A method and system for efficient usage of revision control system resources by providing a client-based file system tree based on managed cache resources is provided. The managed cache resources include both a persistent, disk-based cache that maintains copies of requested file data from a repository server and an ordered tree data structure-based metadata cache for tracking file metadata across revisions. Embodiments of the present invention further maintain in the data cache data related only to specifically requested files. Embodiments of the present invention further track a range of versions of the file system tree for which particular file versions are applicable, so that unnecessary downloading to the client of unchanged files is avoided. Thus, file data and metadata are only requested from a repository server when needed and only a single version of a file is maintained until a modification to that file is made.

A version control system such as may be used in an information management system for a source code development project. Multiple versions of artifacts are stored in the version control system. Some versions are stored in uncompressed form while others are stored in compressed form. The artifacts selected to be stored in compressed form are selected to facilitate rapid retrieval of files. The compression process is such that the compression may be performed as a background operation.

A version control system helps to keep track of versions of process plant items that may represent, or be capable of representing, entities in a process plant. The process plant items may comprise, for example, module objects which may be capable of specifically representing process entities of the process plant. These module objects may be created from module class objects which may be capable of generically representing process entities of the process plant. Version data is stored and associated with a module object. The version data may comprise data indicative of a version of a module class object that was used to create the module object. The version data may also comprise data indicative of a version of the module object. Configuration systems, version control systems, viewing systems, debugging systems, run-time monitoring systems, asset management systems, etc., may examine or permit viewing of the version control data associated with an item.

A method for managing a target file in a version control system is provided. According to this invention, when a user requests to check-out, check-in, update, or add tags to an target file, the version control system operates on a substitute file instead of the target file. The substitute file is generated based on the target file and is much smaller than the target file. Thus, the time for opening and manipulating files can be saved.

Embodiments of the present invention provide a method, system and computer program product for the automated merger of content in progeny of a primary file in a version control system. In one embodiment of the invention, the method can include establishing different segments of content in a primary file in a merger tool executing in memory by a processor of a host computer and associating each of the segments with a classification corresponding to a particular merger rule selected from amongst different merger rules. The method also can include parsing content in different progeny of the primary file and identifying changes in a parsed portion of the progeny corresponding to a specific one of the segments of the primary file. Finally, the method can include applying to the identified changes a merger rule corresponding to a classification associated with the specific one of the segments.

A nonlinear revision control system for images is designed with the common digital editing and sketching workflows in mind. DAG (directed acyclic graph) is used as the core structure and DAG nodes represent editing operations, and DAG edges indicate the corresponding spatial, temporal and semantic relationships. DAG is visualized in RevG (revision graph), which provides not only a meaningful display of the revision history, but also an intuitive interface for common revision control operations such as review, replay, diff, addition, branching, merging, and conflict resolving. Beyond revision control, the system also facilitates artistic creation processes in common image editing and digital painting workflows. A prototype system has been built upon GIMP, an open source image editor, and demonstrates its effectiveness through a formative user study and comparisons with alternative revision control systems.

The invention is suitable for the technical field of software plug-ins, and provides a project automatic-deployment plug-in. The project automatic-deployment plug-in comprises a client plug-in program, a client configuration file and a version control system warehouse information file. The project automatic-deployment plug-in can detect project updating conditions of a code warehouse of a supplier version control system of a software system in a timed mode, updates codes of an appointed version in the version control system to a client server through the internet, and greatly lowers development, updating and maintenance cost of the system.

Disclosed is a file versioning system and corresponding methods for its operation. The file versioning system allows making snapshots of the file system every time there is a modification to the file system or its items. The snapshots may be linked to their immediate predecessors. Some older snapshots may be discarded according to a “thinning out” process based on multiple criteria. The snapshots may be displayed to a user in a manner making it easy to select a desired version.