Software change management extension for uniformly handling artifacts with relaxed contraints
View Patent ↗Software change management (SCM) systems can be extended to uniformly handle artifacts which lack constraints typically imposed on managed items. In the solution, a data type associated with a SCM system can enable management of unmanaged artifacts. Unmanaged artifacts can include, but is not limited to, artifacts which lack can traditional change management constraints, managed artifacts not directly associated with the SCM, artifacts with different constraints than the SCM imposed constraints, and the like. In one embodiment, an unmanaged artifact can have different lifecycles, policies, and the like which can make it unsuitable for traditional management approaches by the SCM. The SCM can utilize the data type to manage unmanaged artifacts without requiring significant change in functionality of the SCM by permitting change management processes to be applied to the unmanaged artifacts.
1. A system for extending software change management to handle unmanaged artifacts comprising:
one or more processors, which are hardware processors;
one or more non-transitory storage mediums storing digitally encoded information;
an object comprising of a reference stored within a software change management (SCM) system, comprising the one or more processors and the one or more non-transitory storage mediums, wherein the reference is a linkage to a remote managed artifact stored within a repository, wherein the at least one reference lacks artifact restrictions, wherein the artifact restrictions are traditional software change management artifact restrictions associated with a managed artifact within the SCM, wherein the object is associated with a binding to the managed artifact stored within the SCM; and
an SCM engine able to perform operations on the object in a manner consistent with a managed artifact; and
a portion of metadata associated with the object, wherein the metadata comprises of at least a name information and a location information associated with the remote managed artifact, wherein the location information is a Uniform Resource Identifier (URI), wherein the URI is associated with a source code repository.
2. The system of claim 1 , wherein the operations are at least one of a fetch operation and a compare operation.
3. The system of claim 1 , wherein the managed artifact is a source code entity, and wherein the portion of metadata is stored within an extensible markup (XML) language file within the SCM, wherein the portion of metadata indicates a means to access the remote managed artifact.
4. The system of claim 1 , wherein the system is a portion of a Web-enabled service.
5. The system of claim 1 , wherein the SCM performs a dependency check on each unmanaged artifact associated with the object.
6. The system of claim 1 , wherein the object comprises of at least one remote managed artifact.
7. The system of claim 1 , wherein the SCM is an IBM RATIONAL ASSET MANAGER software.
8. A computer program product comprising a non-transitory computer readable storage medium having computer usable program code embodied therewith, the computer usable program code comprising:
computer usable program code stored in a non-transitory tangible storage medium, when said computer usable program code is executed by a processor it is operable to store an object within a software change management (SCM) system, wherein the object is managed as a traditional SCM artifact, wherein the object comprises a reference to one or more unmanaged artifacts, wherein the unmanaged artifacts lack restrictions imposed by the software change management system, wherein the unmanaged artifacts are associated with a binding of the traditional SCM managed artifact, wherein the object has associated metadata, wherein the metadata comprises of at least a name information and a location information associated with one of the unmanaged artifacts, which is a remote managed artifact, wherein the location information is a Uniform Resource Identifier (URI), wherein the URI is associated with a source code repository; and
computer usable program code stored in a non-transitory tangible storage medium, when said computer usable program code is executed by a processor it is operable to trigger a programmatic action on the stored object in response to an action associated with at least one of the traditional SCM artifact and the stored object.
9. The computer program product of claim 8 , wherein the traditional SCM artifact is a source code entity, wherein the restrictions that the unmanaged artifacts lack are at least one of a lifecycle, access rule, and a management policy, wherein the binding is a compile time dependency binding, wherein the unmanaged artifacts is associated with a remote repository, wherein within the remote repository, the unmanaged artifacts are managed as another traditional SCM artifact, and wherein the action that triggers the programmatic action is a provisioning action.
10. The computer program product of claim 9 , wherein the provisioning action results in importing at least one unmanaged artifact into a development environment associated with a client computing device.
11. The computer program product of claim 8 , wherein the programmatic action is performed prior to or subsequent to compile time.
12. The computer system of claim 1 , wherein the object is associated with at least one of a source code trunk, a source code branch, and a source code merge of the remote managed artifact.
13. The system of claim 1 , wherein the object comprises a linkage, the linkage coupling a managed artifact stored within the SCM to the remote managed artifact.
14. The system of claim 13 , wherein the coupling is one of a loose coupling and tight coupling, wherein the loose coupling enables minimal constraints on the object and wherein the tight coupling enables rigid constraints on the object.
15. The system of claim 1 , wherein the SCM engine is configured to:
determine automatically one or more managed artifacts dependent on a traditional managed artifact; and
create the object within the SCM system based on the dependency.
16. The computer program product of claim 8 , wherein the object is associated with at least one of a source code trunk, a source code branch, and a source code merge of the remote managed artifact.
17. The computer program product of claim 8 , wherein the object comprises a linkage, the linkage coupling a managed artifact stored within the SCM to the remote managed artifact.
18. The computer program product of claim 8 , wherein the coupling is one of a loose coupling and tight coupling, wherein the loose coupling enables minimal constraints on the object and wherein the tight coupling enables rigid constraints on the object.
19. The computer program product of claim 8 , wherein the SCM engine is configured to:
determine automatically one or more managed artifacts dependent on a traditional managed artifact; and
create the object within the SCM system based on the dependency.