Abstract: In order to facilitate automatic roll-forward updates, embodiments include detecting a failure in a software package. In response to the failure, data indicative of a current version of a software package is extracted from a release directory. In response to the application data, a base repository with a version history of the application is cloned. In response to the cloning, a prior set of changes from the base repository in the temporary directory, where the prior set of changes form an old application version of the application, is imported. In response to the import of the prior set of changes, the current version is overwritten with the prior set of changes to generate a new version. The new version is pushed directly to the base repository and a deployment API causes the new version to replace the current version.

Abstract: A secure live media boot system includes a BIOS that is coupled to a storage subsystem and a non-volatile memory system. The BIOS receives an operating system image. Prior to installing an operating system on a computing device using with the operating system image, the BIOS performs a first measurement action on the operating system image to produce a first operating system measurement that it stores in the non-volatile memory system. The BIOS also stores a read-only version of the operating system image on the storage subsystem. The BIOS subsequently receives a request to install the operating system on the computing device and, in response, performs a second measurement action on the operating system image in order to produce a second operating system measurement. If the BIOS determines that the second operating system measurement matches the first operating system measurement, the BIOS installs the operating system on the computing device.

Abstract: Methods and devices for selecting an application for download for use with hardware on a computer device may include receiving, from a remote application store, application metadata that includes at least one hardware constraint for an application in response to an application request for installation of the application. The methods and devices may include evaluating the application metadata to determine whether the at least one hardware constraint is satisfied on the computer device. The methods and devices may include installing the application when the at least one hardware constraint is satisfied on the computer device.

Abstract: An electronic apparatus has a communication unit, a first storage unit, a second storage unit, and a controller. The communication unit communicates with a terminal apparatus. The first storage unit stores a first program. The second unit stores a patch program for the first program received from the terminal apparatus via the communication unit for each section. When executing the first program, the controller applies the latest patch program stored in each section in the second storage unit.

Abstract: A system such as a service of a computing resource service provider, a directory service, a directory server, or any suitable system includes executable code that, if executed by one or more processors, causes the system to perform a first stage of a multi-stage deployment of a first directory schema by at least providing a second directory schema to a first computer system, wherein the first computer system is associated with a directory configured according to the first directory schema and causing the first computer system to reconfigure the directory according to the second directory schema The system may also determine, based on a result of reconfiguring the directory, whether to proceed to a second stage of the multi-stage deployment of the first directory schema. The system may be utilized as part of a directory schema update process wherein a multi-stage deployment pipeline is utilized.

Abstract: A method and system for upgrading software stored on a hardware unit is provided. The method includes the steps of: (i) connecting a plurality of hardware units to a computer, the computer including an upgrade algorithm; (ii) scanning, by the upgrade algorithm, for the presence of the plurality of hardware units; (iii) querying, by the upgrade algorithm, each of the plurality of hardware units for information about the software stored on the respective hardware unit; (iv) determining, by the upgrade algorithm, that an upgrade is available for the software stored on at least one of the plurality of hardware units; (v) installing the available upgrade on the at least one of the plurality of hardware units; and (vi) receiving, from the upgrade algorithm, an indication that the installation was successful on at least one of the plurality of hardware units.

Abstract: Methods and apparatus to generate a shadow setup based on a cloud environment and upgrade the shadow setup to identify upgrade-related errors are disclosed. An example apparatus includes a topology deployment determiner to deploy a shadow setup corresponding to a replica version of a live cloud environment; an upgrade coordinator to upgrade one or more components of the shadow setup; and a reporter to generate a report corresponding to the upgrade.

Abstract: The present invention relates to an electronic device, a compiling method, and a computer-readable recording medium. An electronic device according to an embodiment of the present invention compiles a source code of a dynamic programming language compiled during execution of a program to the level of a static programming language compiled before execution, and may comprise a processor which determines whether the source code of the dynamic programming language generated when a command for operating the program is received can be processed by the first compiler in the same manner as the source code of the static programming language processing, and converts the source code of the dynamic programming language by the first compiler if the code can be processed as a result of the determination.

Abstract: A memory clean up mechanism may dynamically calculate the amount of free memory required and then identify a list of unused applications that may be automatically deleted to reach the required free memory.

Abstract: In order to facilitate automatic roll-forward updates, embodiments include detecting a failure in a software package. In response to the failure, data indicative of a current version of a software package is extracted from a release directory. In response to the application data, a base repository with a version history of the application is cloned. In response to the cloning, a prior set of changes from the base repository in the temporary directory, where the prior set of changes form an old application version of the application, is imported. In response to the import of the prior set of changes, the current version is overwritten with the prior set of changes to generate a new version. The new version is pushed directly to the base repository and a deployment API causes the new version to replace the current version.

Abstract: Embodiments of the present disclosure provide methods, systems, apparatuses, and computer program products that provide for an improved and more efficient system of networked computing devices. The embodiments disclose an apparatus and system that enable client devices to install integrations of a third party application that supports variable host address identification. The apparatus and methods further enable a user of the client device to modify the host address identification associated with an installed integration. In this manner, the group-based communication system establishes communication links with network locations that vary from integration to integration and that may vary over time. To implement the invention, the group-based communication system supports the creation of a blueprint application, with an associated blueprint row that serves as the basis from which a plurality of differing integrations are generated. Further, the blueprint row stores variable host address identifications.

Abstract: Unused instructions and no longer used instructions in a target application binary are determined. The target application binary is rewritten before and after runtime execution of the target application binary to remove the unused and no longer used instructions to reduce binary attack surface area for the runtime execution of the target application binary. Methods, computer systems, and computer program products are disclosed.

Abstract: Techniques for configuring and validating a data pipeline system deployment are described. In an embodiment, a template is a file or data object that describes a package of related jobs. For example, a template may describe a set of jobs necessary for deduplication of data records or a set of jobs performing machine learning on a set of data records. The template can be defined in a file, such as a JSON blob or XML file. For each job specified in the template, the template may identify a set of dataset dependencies that are needed as input for the processing of that job. For each job specified in the template, the template may further identify a set of configuration parameters needed for deployment of the job. In an embodiment, a server uses the template and the configuration parameter values collected via the GUI to generate code for the package of jobs. The code may be stored in a version control system. In an embodiment, the code may be compiled, executed, and deployed to a server for processing the data.

Abstract: An application is defined including an application implementation and a deployment application including design-time artifacts. Persistence artifacts are modeled as content for the deployment application. Persistence artifacts needed at runtime are generated using implemented software code for the application implementation and the generated persistence artifacts are added to the modeled persistence artifacts. The defined application is added to a multi-tenancy-enabled multi-target application (MTA) associated with the defined application and comprising a set of modules. The MTA is stored into a versioned artifact repository. An MTA deployment service is triggered to deploy the MTA and the application associated with the MTA is started.

Abstract: Providing differing degrees of reliability or security for distinct devices within a reliable distributed system. Allowing virtual machines to operate in a reliable distributed system without either exposing the actual available devices to guest operating systems, or requiring the guest OS to maintain, or to maintain information about, reliability or security. Methods are responsive to a hierarchy of possible reliability or security failures, to guard more carefully against simultaneous failures of reliability or breaches of security, without additional work or delay. Functions invoked by the user that relate to reliability and security are hidden, so the user can specify a degree of reliability or security without having to implement those requirements themselves. Providing a uniform set of resources available to all users, separating out those individual resources that are allocated to particular users, and emulating particular devices at the request of those particular users.

Abstract: A method and system for deploying third party device services through an enclosed appliance interface using containers. Specifically, the disclosed method and system entail employing a generic plugin to facilitate the integration and execution of custom, third-party plugins onto the framework of a platform. The custom, third-party plugins, via the generic plugin, perform hardware device operations as secured and sandboxed computer processes (i.e., containers), which are stateless, and thus, fail to cause idling across computer processor and memory usage.

Abstract: Techniques for automatically ingesting progressive web apps (PWAs) into an application store of an operating system (OS) are provided. According to one set of embodiments, a computer system can receive a list of PWAs identified via crawling one or more websites. For at least one PWA in the list, the computer system can convert the PWA into a native application that is native to the OS of the application store. The computer system can then make the native application available through the application store for discovery by a user and for installation on a client device of the user.

Abstract: Examples include a user segmentation system for staged application rollout. In an example, an application usage engine receives data for users including a number of screens used in an application version and a number of user actions used in the application version. A staged rollout engine determines, for each user, an early adopter probability based on the number of screens used in the application version and the number of user actions used in the application version, and in some examples a preconfigured factor or weighting. For a subsequent application version, staged rollout groupings are determined. Users are assigned to staged rollout groupings based on the early adopter probabilities.

Abstract: The application pertains to the automated deployment of software packages to an enterprise's testing, staging and production environments. It does this by detecting events with respect to the enterprise's code base and, upon detection of a change in a package, identifies the application(s) that include that package. For each such application, a workflow is provided defining a pipeline of environments in which a bundle of packages that make up that application are to be installed for testing, staging or production. A software package in which an event has occurred is installed in those environments on a stepwise basis per that workflow and the application is (re)built there for testing, etc. A status of the bundle of packages that make up an application in each of the respective environments is shown in a graphical user interface.

Abstract: An installation tool includes a memory, a retrieval engine, an extraction engine, a configuration engine, a compiler, and an installer. The memory stores installation parameters of a previous software update for an application. The retrieval engine receives a request to install a first software update for the application and in response to the request, retrieves the installation parameters of the previous software update. The extraction engine extracts from the application a plurality of source binary files for the application. The configuration engine receives a plurality of requirements for installing the first software update based upon the retrieved installation parameters. The compiler creates an installation executable for the first software update based upon the plurality of source binary files and the plurality of requirements. The installer executes the installation executable to apply the first software update according to the plurality of requirements.