A hotfix method and apparatus are provided. The method comprises: compiling each SDK to obtain a compiled file of each SDK, a project to be fixed comprising at least two SDKs having a dependency relationship, and the compiled file of each SDK comprising an instrumentation code of each method to be fixed; if target methods to be fixed exist in the plurality of SDKs, retaining the instrumentation codes of said target methods in one of the SDKs, and deleting the instrumentation codes of said target methods in other SDKs; generating a hotfix patch, the hotfix patch comprising a patch corresponding to the instrumentation code of each method to be fixed; and when an access end accesses the compiled file of the at least one SDK of the project to be fixed, sending the hotfix patch to the access end.

Embodiments of the present disclosure relate to systems and methods for generating delta-difference on an on-demand basis. A delta-difference generation service receives, from each of one or more of a plurality of nodes, a list of packages for which the node wishes to subscribe to the delta-difference generation service. Each of the one or more nodes may include in their list those packages that may benefit the most from use of the delta-difference generation service have based on a variety of factors such as package update frequency and resource availability of the node. In response to receiving an updated version of a package included in a list received from any of the one or more nodes, a delta-difference between a current version and the updated version of the package may be generated and transmitted to each of the one or more nodes that included the package in their respective list.

Embodiments of the present disclosure relate to systems and methods for generating delta-difference on an on-demand basis. A delta-difference generation service receives, from each of one or more of a plurality of nodes, a list of packages for which the node wishes to subscribe to the delta-difference generation service. Each of the one or more nodes may include in their list those packages that may benefit the most from use of the delta-difference generation service have based on a variety of factors such as package update frequency and resource availability of the node. In response to receiving an updated version of a package included in a list received from any of the one or more nodes, a delta-difference between a current version and the updated version of the package may be generated and transmitted to each of the one or more nodes that included the package in their respective list.

A system may include multiple software components of a software application running on multiple nodes in a distributed computing system, a patch execution server including a patch build server including a structured patch execution module connected to the distributed computing system via a network. The patch execution module receives an uploaded patch, a patch definition file, and a workflow template from a global patch repository. Further, the patch execution module creates a patch definition file for the patch using an associated patch master file, an associated build definition file, and an associated product definition file. Furthermore, the patch execution module creates a workflow template using the patch definition file and the patch. Also, the patch execution module creates a workflow file using node information associated with the multiple nodes and the workflow template. In addition, the patch execution module executed the patch, using the patch, patch definition file and the workflow file, across the multiple nodes in the distributed computing system.

A system may include multiple software components of a software application running on multiple nodes in a distributed computing system, a patch execution server including a patch build server including a structured patch execution module connected to the distributed computing system via a network. The patch execution module receives an uploaded patch, a patch definition file, and a workflow template from a global patch repository. Further, the patch execution module creates a patch definition file for the patch using an associated patch master file, an associated build definition file, and an associated product definition file. Furthermore, the patch execution module creates a workflow template using the patch definition file and the patch. Also, the patch execution module creates a workflow file using node information associated with the multiple nodes and the workflow template. In addition, the patch execution module executed the patch, using the patch, patch definition file and the workflow file, across the multiple nodes in the distributed computing system.

In accordance with embodiments, there are provided mechanisms and methods for creating, exporting, viewing and testing, and importing custom applications in a multitenant database environment. These mechanisms and methods can enable embodiments to provide a vehicle for sharing applications across organizational boundaries. The ability to share applications across organizational boundaries can enable tenants in a multi-tenant database system, for example, to easily and efficiently import and export, and thus share, applications with other tenants in the multi-tenant environment.

In accordance with embodiments, there are provided mechanisms and methods for creating, exporting, viewing and testing, and importing custom applications in a multitenant database environment. These mechanisms and methods can enable embodiments to provide a vehicle for sharing applications across organizational boundaries. The ability to share applications across organizational boundaries can enable tenants in a multi-tenant database system, for example, to easily and efficiently import and export, and thus share, applications with other tenants in the multi-tenant environment.

Disclosed herein are methods, computer readable media, and devices for performing software updates. In one embodiment, a method is disclosed comprising initializing a storage space of a secure storage device into a plurality of portions; copying an update program to a first portion in the portions and copying update data to a second portion of the portions; generating a first golden measurement for the first portion and a second golden measurement for the second portion; measuring the first portion; updating or rolling back an update to the secure device in response to determining that the measuring of the first portion does not match the first golden measurement of the first portion; and verifying an update operation upon determining that the measuring of the first portion matches the first golden measurement of the first portion.

A method, edge node application investigator, computer program and computer program product for for updating an edge node of a process control system using an information model for the edge node, where the information model representing the edge node as an object to which one or more application objects are linked, which application objects represent applications that are provided for being run by the edge node as well as to a process control system including such an edge node application investigator. The edge node application investigator compares applications of the edge node with the application objects in the information model and changes the applications of the edge node, if there is a deviation between the applications of the edge node and the application objects of the information model, so that the applications of the edge node correspond to the application objects of the information model.

A vehicle software upgrade method for obtaining a to-be-upgraded software version of a vehicle. When a vehicle performs the software upgrade method, the vehicle determines a current location of the vehicle, and determines whether the vehicle is located within a rescue range of a service site. Then, the vehicle sends, to the cloud server, information that includes a determining result and a to-be-upgraded version of software currently installed on the vehicle. The cloud server pushes to the vehicle, based on the obtained information, an installation package type corresponding to the to-be-upgraded software version. Then, the vehicle determines, how to perform upgrade.