Abstract: Extensible change control management for development and deployment of applications is described. A change control manager may register plugin components, including requester, approver and performer components, to process changes to a resource of a resource type, where registering is performed responsive to request(s) received via programmatic interface(s). Upon receiving a change request from the requester component, the change control manager may send the change request to the approver component to approve the change request and, responsive to notification of approval from the approver component, the change control manager may then send the change request to the performer component to implement the requested change.

Abstract: Extensible change control management for development and deployment of applications is described. A change control manager may register plugin components, including requester, approver and performer components, to process changes to a resource of a resource type, where registering is performed responsive to request(s) received via programmatic interface(s). Upon receiving a change request from the requester component, the change control manager may send the change request to the approver component to approve the change request and, responsive to notification of approval from the approver component, the change control manager may then send the change request to the performer component to implement the requested change.

Abstract: Translations between versions of data object schemas may be performed between data object producers and data object consumers. A request to update a data object may be an update according to an additional version of a schema applicable to the data object from an existing version of a schema. The data object may be provided by one component of a distributed system. A trigger event may be detected to send the data object to a different component of the distributed system. The data object may be translated from the additional version to the existing version and sent to the different component.

Abstract: A separate relationship management interface for applications that utilize application data objects to implement various application features is used to track changes to relationships between application data objects. Requests that cause writes corresponding to relationships between application data objects and requests that cause reads of relationships between application data objects may be handled using an interface that interacts with a separate data store tracking the relationships between application data objects.

Abstract: A computing resource service provider may operate a build service configured to store data object on behalf of a customer of the computing resource service provide. The build service may receive a stream of data objects including object objects that reference one or more other data objects. A Bloom filter may be used to determine whether a one or more referenced data objects have been previously processed by the build service. This may enable the build service to reorder processing of the data object based at least in part on whether the one or more referenced data objects have previously been processed by the build service.

Abstract: Computing systems executing applications may receive updates to the application from an update service. The update service may generate an update bundle including resources of the application. The update bundle may further include a manifest containing information identifying the resources and a location for the resources to be stored within the computing system. Additionally, the computing system may maintain a cache of previously received resources.

Abstract: Technologies are described herein for use in identifying and resolving software issues. One or more corrective actions may be identified and taken that are based upon the similarity between an unresolved issue and one or more resolved issues and/or upon the similarity between code changes made to resolve similar previously resolved issues. A version control graph might also be utilized to determine if a change made to resolve an issue in one branch of a software component is applicable to another branch of the software component. The version control graph might also be utilized to compute the relevance of an entry in an issue tracking system for an issue at a point in time after the entry is created in the issue tracking system.

Abstract: Technologies are described herein for distributed storage and retrieval of directed acyclic graphs, such as version control graphs maintained by a version control system. In order to store data contained in a directed acyclic graph, objects stored in the graph may be grouped into chunks utilizing a relatedness heuristic. The chunks may then be stored in a distributed object store. An index to the objects stored in the chunks may also be created that includes an index entry for each object. The index entry for each object includes a unique identifier for the object and data identifying the location of the object in the distributed object store. The index may be utilized to traverse the directed acyclic graph and to obtain all or a portion of the objects in the directed acyclic graph from the distributed object store.

Abstract: Technologies are described herein for synchronization of source code objects and software development workflow objects. Software development workflow objects are identified that are related to source code objects to be synchronized to a development device. The identified software development workflow objects are then stored in a copy of a source control object store that also includes the source code objects to be synchronized. The copy of the source control object store may then be transmitted to the development device for offline use. Tools might also be provided on the development device for utilizing the software development workflow objects stored in the copy of the source control object store maintained by the development device. The copy of a source control object store containing modified source code objects and modified software development workflow objects might also be utilized to synchronize the changes to the objects to an appropriate object store.

Abstract: Technologies are described herein for use in identifying and resolving software issues. One or more corrective actions may be identified and taken that are based upon the similarity between an unresolved issue and one or more resolved issues and/or upon the similarity between code changes made to resolve similar previously resolved issues. A version control graph might also be utilized to determine if a change made to resolve an issue in one branch of a software component is applicable to another branch of the software component. The version control graph might also be utilized to compute the relevance of an entry in an issue tracking system for an issue at a point in time after the entry is created in the issue tracking system.

Abstract: Technologies are described herein for performing a defect analysis on a software component based upon collected data that describes the operational state of hardware devices in an execution environment utilized to execute the software component at different points in time. The hardware state data is collected from the hardware devices in the execution environment at different points in time and stored in a version control system. A defect analysis may then be performed for an issue identified in the software component utilizing the hardware state data stored in the version control system. Based upon the results of the defect analysis, one or more actions may be taken such as, but not limited to, rolling the hardware or software configuration of one or more of the hardware devices in the execution environment back to a previous point in time.

Abstract: Technologies are described herein for use in identifying and resolving software issues. One or more corrective actions may be identified and taken that are based upon the similarity between an unresolved issue and one or more resolved issues and/or upon the similarity between code changes made to resolve similar previously resolved issues. A version control graph might also be utilized to determine if a change made to resolve an issue in one branch of a software component is applicable to another branch of the software component. The version control graph might also be utilized to compute the relevance of an entry in an issue tracking system for an issue at a point in time after the entry is created in the issue tracking system.