47 results about "Software build" patented technology

A data processing system implements obtaining build logs that include information associated with a software build problem; analyzing the logs to generate a knowledge graph identifying the relationship between various entities in the logs; extracting a signature of a candidate root cause of the build problem from the knowledge graph representing a subset of nodes and edges of the knowledge graph; providing the signature of the candidate root cause to a graphical language model to obtain a prediction of a category of root cause failure selected from among a plurality of root cause failures; constructing a prompt for a language model to generate a root cause failure analysis that describes the root cause of the build problem, the prompt including the category of root cause; receiving the root cause failure analysis from the language model; and performing one or more actions in response to receiving the root cause failure analysis.

Techniques are described for validating build integrity of software products, such as applications or containers. More specifically, this disclosure describes a build integrity validation system that analyzes build artifacts resulting from a software build process to create source code assertions, and compares the assertions against the source code from which the build artifacts were produced. The build integrity validation system validates that a particular build artifact is producible by the source code to ensure that no additional code was introduced during the build process. The build integrity validation system may also reverse the analysis to validate that the source code is able to produce the build artifacts to ensure that no code was removed or modified during the build process. The build integrity validation system identifies and reports identified discrepancies between the source code and the build artifacts resulting from the software build process of the source code.

Techniques are described for a model-based process to validate build integrity of software products. A build integrity validation system generates a build artifact model including one or more software components extracted from a build artifact resulting from a software build process of source code and generates a source code including one or more software components extracted from the source code. The system compares the software components of the build artifact model and the software components of the source code model, and identifies at least one discrepancy between the build artifact model and the source code model. The system determines a level of risk associated with the at least one discrepancy and, in response to determining the level of risk associated with the at the least one discrepancy, generates a decision indicating whether the at least one build artifact is approved for use in a software product.

A method comprises generating, during a software build process conducted in a trusted build environment, a trusted log comprising a plurality of records of actions performed during the software build process and a plurality of identifiers of tools used to perform the actions, aggregating the plurality of records of actions and the plurality of identifiers into a build certificate file, generating a digital signature to be applied to the build certificate, and publishing the build certificate in association with one or more build artifacts generated by the software build process.

Modifications to existing computer hardware, compiler changes or source-to-source transforms performed during the software build process, and a collection of libraries and modifications to existing standard system software and libraries. The invention allows a program author to enforce various kinds of locality of causality in software to provide enforcement of boundaries for the following aspects of a computer program: control, space, time, modularity, reference, initialization, and mutability. Where these properties do not suffice to guarantee a property at static time, dynamic checks may be added and the constraints on control flow prevent such dynamic checks from being avoided by the program.

Techniques are described for securing secrets in software build workflows. In some implementations, build instructions call for execution of a first program module and a second program module, where the first program module has been approved to make a privileged request, but the second program module has not. The first program module can be stored in a trusted repository, separately from the second program module. When the first program module is loaded for execution, a cryptographic signature can be validated to determine that the first program module is authentic and as a condition for passing a privileged credential to the first program module. The second program module has no access to the privileged credential. Instead, when the second program module is loaded for execution, a determination can be made whether the second program module makes any privileged requests. Any privileged requests from the second program module will not be fulfilled.

The disclosed system and process involve correlating outbound traffic with a CI / CD pipeline. CI / CD Pipelines consist of multiple jobs, and each job's steps execute on the same runner host. Network monitors relay information about domain names and network connections during job execution to the data store. Once all pipeline jobs are complete, the correlation server links domain names and connections to determine endpoints. This correlation, showing outbound traffic for each step, is accessible to the pipeline owner for review. An alert is triggered for new endpoints relative to the baseline. Owners can block unexpected endpoints based on explicitly defined lists. The correlation server also identifies file events, aiding in detecting suspicious file and software build overwrite events for combating software supply chain attacks. Observed file and network events contribute to generating a Software Bill of Materials (SBOM) through runtime events.

Techniques are provided for building software using volume snapshots. One method comprises obtaining a volume snapshot of a workspace, wherein the volume snapshot comprises software files associated with a software development project; creating a new workspace from the volume snapshot; applying updates to the new workspace by fetching, from a software development system, code updates to the software files; and performing a software build on the new workspace to compile source code associated with the software files. The new workspace may be created from the volume snapshot using a read-only layer of the volume snapshot and the updates to the new workspace may employ a read-write layer of the volume snapshot. A volume snapshot may be created, in response to a validation of software files, using a given workspace and the updates to the given workspace.

A method includes receiving a software build task, identifying one or more previously executed software build tasks in view of one or more properties of the software build task and determining a set of computing resources to be allocated to a build container for performing the software build task in view of the one or more previously executed software build tasks. The method further includes generating the build container to perform the software build task.

A data processing system implements obtaining build logs that include information associated with a software build problem; analyzing the logs to generate a knowledge graph identifying the relationship between various entities in the logs; extracting a signature of a candidate root cause of the build problem from the knowledge graph representing a subset of nodes and edges of the knowledge graph; providing the signature of the candidate root cause to a graphical language model to obtain a prediction of a category of root cause failure selected from among a plurality of root cause failures; constructing a prompt for a language model to generate a root cause failure analysis that describes the root cause of the build problem, the prompt including the category of root cause; receiving the root cause failure analysis from the language model; and performing one or more actions in response to receiving the root cause failure analysis.

Discussed herein are devices, systems, machine-readable media, and methods for assessing a software build for a vulnerability, generating release recommendations, and implementing a remedial action to mitigate security risks. A method includes receiving a Software Bill of Materials (SBOM) that lists one or more libraries used in a software build, receiving a user-specified administration policy, generating an over overall provenance bundle from a metadata of the one or more libraries used in the software build, implementing a gradient boosted tree algorithm using both the overall provenance bundle and the user-specified administration policy to generate a software releasability recommendation, receiving the software releasability recommendation into a Large Language Model (LLM) to generate a recommendation report detailing one or more software vulnerabilities, and implementing the software releasability recommendation by releasing the software build or blocking the release of the software build based on the software releasability recommendation.

Modifications to existing computer hardware, compiler changes or source-to-source transforms performed during the software build process, and a collection of libraries and modifications to existing standard system software and libraries. The invention allows a program author to enforce various kinds of locality of causality in software to provide enforcement of boundaries for the following aspects of a computer program: control, space, time, modularity, reference, initialization, and mutability. Where these properties do not suffice to guarantee a property at static time, dynamic checks may be added and the constraints on control flow prevent such dynamic checks from being avoided by the program.

The present invention provides a multi-objective optimization method for a bubbling column carbon capture process based on a surrogate model, comprising the following steps: constructing a physical simulation model of a packed bubbling column reactor through COMSOL Multiphysics software; sampling in the design domain by the optimal Latin hypercube method according to preselected optimization objectives and design variables; constructing an adaptive hybrid surrogate model, training the model using simulation results, and evaluating the accuracy and stability of the model using R<supgt;2< / supgt> and RMSE, etc.; performing Sobol global sensitivity analysis on different design variables; solving the multi-objective optimization of the selected surrogate model using the non-dominated genetic algorithm II; drawing a Pareto front plot based on the solution set obtained by NSGA-II to obtain the optimal solution of the multi-objective optimization; outputting a multi-objective optimization scheme that meets the pre-specified process requirements, obtaining the best trade-off solution between the energy consumption required for the process and the carbon dioxide capture rate and the corresponding optimal operating conditions, and these data have guiding significance for the subsequent industrial application of the process.

This application relates to the field of computer software technology, providing an image management method, system, and computing device. The method is applied to a computing device equipped with a software integration system, including: responding to a code repository corresponding to the software integration system receiving a commit instruction, detecting the change status of the image configuration file; the change status is used to identify whether any instruction text in the image configuration file has changed; if the change status is "changed," loading the changed image configuration file; generating an image build instruction based on each instruction text in the image configuration file; generating an image file according to the image build instruction; and storing the image file in the image repository of the software integration system. Based on this solution, the computing device utilizes changes to the image configuration file to trigger the automatic generation and updating of image files, decoupling the image file generation process from the software package delivery request, avoiding repeated image building for each package delivery, and improving software build efficiency.

A software build environment is scanned for one or more potentially malicious code paths. In response to scanning the software build environment for the one or more potentially malicious code paths, one or more potentially malicious code paths are identified. The identified one or more potentially malicious code paths comprise at least one of: a typo squat code path, a dependency confusion code path, and a brandjack code path. In response to identifying the one or more potentially malicious code paths a microprocessor does at least one of: generate a notification identifying the one or more potentially malicious code paths, automatically change and / or remove the one or more potentially malicious code paths and deny the start of a build process.

Systems and methods are provided for automatically building software in a secure environment. A system includes a software development environment, having an associated security level. The software development environment generates an encrypted software module containing a software module and a cryptographic hash representing a content of the software module and provides it to a software repository. The software repository, in response to receipt of a build plan, decrypts the encrypted software module to recover the software module and the cryptographic hash representing the content of the software module, generates a new cryptographic hash for the software module, and verifies that the new cryptographic hash matches the cryptographic hash representing the content of the software module. A build environment receives the plurality of software modules from the software repository and generates a software build from the plurality of software modules based upon the build plan.

Techniques are provided for managing software artifact snapshot repositories using definition files. One method comprises obtaining a definition file for a software artifact snapshot repository to be created in association with a given software application, wherein the definition file comprises information characterizing software artifacts used by the given software application to be included in the software artifact snapshot repository; and creating the software artifact snapshot repository, using the definition file, with the one or more software artifacts, wherein a software build of the given software application obtains at least some of the software artifacts using the created software artifact snapshot repository. At least some of the software artifacts included in the software artifact snapshot repository may be automatically updated in response to determining that a content of the software artifact snapshot repository does not match a current version of the definition file.

The embodiment of the invention discloses an external formula editing component calling method and device for an artificial intelligence proposition, equipment and a storage medium. The external formula editing component calling method comprises the following steps: in response to a request of an application platform, creating an OLE container on the application platform, and creating a component identifier of an external formula editing component; the external formula editing component comprises a desktop formula editor component or a third-party office software built-in formula component; in response to a formula editing requirement of an application platform, obtaining a component identifier through the COM component registry; dynamically loading the external formula editing component into an OLE container based on the component identifier; and the function calling of the application platform on the external formula editing component is realized through the IIDspatch interface of the external formula editing component. By means of the mode, cross-platform calling of the external formula editing assembly is achieved, a user can call the external formula editing assembly on the application platform, operation is convenient and efficient, and the problem of formula errors caused by cross-platform use is avoided.

A system for software testing includes a storage device to store screenshots of a user application captured during execution of the user application. The system includes a computer vision device coupled to the storage device. The computer vision device can receive a description of an assertion to be detected within the screenshots. The computer vision device can scan the screenshots to detect presence of the assertion and provide an output indicating presence of the assertion. The screenshot can be stored in a way to associate the screenshot with a software build version or date to indicate a point at which the assertion was introduced into relevant software source code.

Techniques are described for validating build integrity of software products, such as applications or containers. More specifically, this disclosure describes a build integrity validation system that analyzes build artifacts resulting from a software build process to create source code assertions, and compares the assertions against the source code from which the build artifacts were produced. The build integrity validation system validates that a particular build artifact is producible by the source code to ensure that no additional code was introduced during the build process. The build integrity validation system may also reverse the analysis to validate that the source code is able to produce the build artifacts to ensure that no code was removed or modified during the build process. The build integrity validation system identifies and reports identified discrepancies between the source code and the build artifacts resulting from the software build process of the source code.

Described is a technique for securing a private secret key during a software build process for a software development kit (SDK) that includes a code implementation for an application programming interface (API), where the private secret key is for use in signing the payload of an API request for the API. Consistent with examples, a keychain service stores a private secret key. In at least one source code file for a SDK, the source code includes a macro definition, which, upon executing by a compiler, obtains a value for the private secret key. In a programming shell environment, a shell script is executed. Execution of the shell script results in executing a nested script, which queries the keychain service for the private secret key. The shell script then passes the private secret key to a build script of an automated software build tool / system, which injects the private secret key into the source code file at compile time by execution of the macro, resulting in a software product capable of using the private secret key to sign or encrypt the payload of one or more API requests.

Systems and methods providing a processing device to receive, by a software build process executing in a trusted execution environment (TEE) of a first computer system, software source code from a second computer system. The processing device generates a software package by compiling the software source code. The processing device also receives, from the second computer system, a signing key associated with the second computer system. The processing device further signs the software package using the signing key associated with the second computer system. The processing device then deploys the signed software package on the first computer system.

Techniques for providing a QA run cycle and report generation system are provided. In one technique, a user interface (UI) tool retrieves first software testing result data that was generated based on a first type of software test of a software build. The UI tool also retrieves second software testing result data that was generated based on a second type of software test of the software build. In response to receiving first input that selects the first software testing result data, the UI tool updates a UI to present first data that is based on a portion of the first software testing result data. In response to receiving the second input that selects the second software testing result data, the UI tool updates the UI to present second data that is based on a portion of the second software testing result data.

System (100) for continuous root cause analysis of mobile applications via integrated QA-SRE feedback loops, wherein the system comprises the following: a data aggregation module configured to collect structured and unstructured data from test environments, production logs, telemetry, and user feedback; a correlation engine configured to analyze and link quality assurance (QA) test failures with production-level anomalies using pattern recognition and historical mapping; an anomaly detection module that can be operated to detect deviations in application performance using artificial intelligence or machine learning algorithms; a root cause analysis module configured to isolate defects by analyzing stack traces, log events, system resource usage, and device metadata; a feedback loop manager configured to facilitate automated bidirectional communication between QA teams and Site Reliability Engineering (SRE) teams; a recommendation engine configured to generate prioritized problem-solving suggestions based on historical bug data and code commit histories; a context-aware logging module configured to capture runtime environment metadata during both test and production execution; and a central orchestration dashboard coupled with a version control integrator and configured to visualize system insights and link problems to specific software builds or deployments; the system enables real-time detection, diagnosis, and resolution of application problems throughout the entire lifecycle of the mobile application.

Described is a technique for securing a private secret key during a software build process for a software development kit (SDK) that includes a code implementation for an application programming interface (API), where the private secret key is for use in signing the payload of an API request for the API. Consistent with examples, a keychain service stores a private secret key. In at least one source code file for a SDK, the source code includes a macro definition, which, upon executing by a compiler, obtains a value for the private secret key. In a programming shell environment, a shell script is executed. Execution of the shell script results in executing a nested script, which queries the keychain service for the private secret key. The shell script then passes the private secret key to a build script of an automated software build tool / system, which injects the private secret key into the source code file at compile time by execution of the macro, resulting in a software product capable of using the private secret key to sign or encrypt the payload of one or more API requests.

A software build tool system and method for generating and validating a software build for execution on a target hardware device of an embedded system. The system includes: a user interface subsystem configured for receiving build parameter data pertaining to software from a user; a build tool subsystem configured for receiving the build parameter data from the user interface subsystem and building the software to generate a software build for execution on a target hardware device of an embedded system; and a memory reporter subsystem configured for receiving the software build generated by the build tool subsystem and providing access to target hardware build validation data resulting from and / or used as a part of the software build during execution.

System and method for an in-vehicle network comprising a microcontroller unit (MCU) located within the vehicle, which includes an internal Ethernet switch and an auxiliary core manager, wherein the MCU hosts one or more software builds and the auxiliary core manager manages the internal Ethernet switch and the software builds. An external Ethernet switch located within the vehicle connects one or more ports of the internal Ethernet switch to one or more devices through one or more virtual local area networks (VLANs), wherein, upon a reflash event, the auxiliary core manager generates a VLAN configuration and filter rule for the internal switch that associates the software builds with the MCU ports based on a MAC and IP address of each MCU port.

A computer-implemented method according to one approach, is for customizing the selection of stages in a multi-stage software build. The computer-implemented method includes: using information associated with the multi-stage software build to develop situational context of the multi-stage software build. The situational context is converted into a build context and the build context is further converted into a number of build stages. Moreover, the build stages are automatically edited, and the edited stages are executed.

A method and apparatus of a device that builds a target using a plurality of processing units is described. In an exemplary embodiment, the device receives a build file for the target, where the build file identifies a plurality of dependencies and the first target is depended on a second target. In addition, the device generates a directed acyclic graph for the first target from the plurality of dependencies. Furthermore, the device transforms the directed acyclic graph by transforming the first set of dependencies to a second set of dependencies and the second set of dependency includes the first dependency that is from a first node in the first target to a second node of a second target. The device additionally identifies a plurality of independent executable tasks, where each of the plurality of independent executable tasks is executable without an unresolved dependency and at least one of the plurality of executable tasks is associated with the second set of dependencies of the transformed directed acyclic graph. The device further schedules the plurality of independent executable tasks on the plurality of processing units. In addition, the device concurrently executes the plurality of independent executable tasks.

The invention relates to a security method for programming a computer program on a control unit, comprising the following steps executed by a processor in a software build environment in the order mentioned: a. Providing a complete computer program containing user data in a first data format; b. Converting the payload data from a first data format into a second data format and using a flash toolchain adapting the data for infrastructure data and creating a plurality of separate flash containers therefrom, where security mechanisms are checked and checksums are created using the Flashtoolchain, and wherein such a flash container in the second data format comprises payload data with at least one logical block based on at least part of the provided computer program, as well as infrastructure data; c. Flashing at least one flash container created using the flash tool chain from the SoftwareBuild environment to a control unit using a flash tool; d. Uploading at least a portion of the at least one flash container from the control unit to the SoftwareBuild environment; and e. in the SoftwareBuild environment, comparing the uploaded portion of the payload with the originally provided payload and forming a difference. With the validation procedure proposed here, the error-free adaptation of the infrastructure data of a control unit can be reliably verified.