SOFTWARE ARTIFACT MANAGEMENT SYSTEMS AND METHODS

• US 20190317756A1
• Filed: 04/10/2019
• Published: 10/17/2019
• Est. Priority Date: 04/11/2018
• Status: Active Application

• Current Assignee: Walmart Apollo, LLC (WalMart Inc.)
• Original Assignee: Walmart Apollo, LLC (WalMart Inc.)
• Inventors: Bough, Rick J, Vanderpool, Trey, Ulrich, Richard, Blass, Oscar, Longenecker, Ron
• Application Number:
  US16/380,371
• Publication Number:
  US 20190317756A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A package management system for binary files that include executable instructions (such as executable files, statically linked libraries, and dynamically linked libraries). The system comprises a packager configured to identify a plurality of build artifacts used to create an original binary file, and create and store an augmented binary file comprising the plurality of build artifacts appended to the original binary file, such that the augmented binary file has the same functionality when executed as the original binary file. The system can further include an extractor configured to receive the augmented binary file and produce an output comprising the plurality of build artifacts from the augmented binary file.

Claims

1. A package management system for binary files including executable instructions, the system comprising:

a packager configured to;

identify a plurality of build artifacts used to create an original binary file, and

create and store an augmented binary file comprising the plurality of build artifacts appended to the original binary file, the augmented binary file having the same functionality when executed as the original binary file; and

an extractor configured to receive the augmented binary file and produce an output comprising the plurality of build artifacts from the augmented binary file.

2. The system of claim 1, wherein the packager is further configured to retrieve one or more prerequisite build artifacts, each prerequisite build artifact required to create at least one of the plurality of build artifacts, and to add the one or more prerequisite build artifacts to the plurality of build artifacts.

3. The system of claim 2, wherein the packager is configured to add the prerequisite build artifacts to the plurality of build artifacts by:

creating an augmented build artifact comprising a build artifact and the prerequisite build artifacts required to create the build artifact; and

adding the augmented build artifact to the plurality of build artifacts.

4. The system of claim 1, wherein the packager is further configured to append a bill of materials to the augmented binary file, the bill of materials comprising data identifying each build artifact of the plurality of build artifacts;

and

further comprising a program information tool configured to receive the augmented binary file and produce an output comprising the bill of materials.

5. The system of claim 1, wherein the packager is configured to append the plurality of build artifacts to the original binary file by combining the plurality of build artifacts into an archive file and appending the archive file to the original binary file.

6. The system of claim 1 wherein each build artifact of the plurality of build artifacts has a type selected from the group consisting of:

source code file, source code directory structure, library file, build parameter, build script, system components, build machine configuration, and build machine image.

7. The system of claim 1, wherein the packager is further configured to encrypt the plurality of build artifacts such that the extractor requires a decryption key to produce an output comprising the plurality of build artifacts from the augmented binary file.

8. The system of claim 1, wherein the packager is further configured to retrieve the plurality of build artifacts from one or more source code repositories.

9. The system of claim 1, wherein the extractor is further configured to build a new executable using the plurality of build artifacts of the received augmented binary file.

10. The system of claim 1, wherein the packager is further configured to append an identification signature to the augmented binary file.

11. The system of claim 9, wherein the identification signature is recognizable by a software auditing tool.

13. The method of claim 11, further comprising:

retrieving one or more prerequisite build artifacts, each prerequisite build artifact required to create at least one of the plurality of build artifacts; and

adding the one or more prerequisite build artifacts to the plurality of build artifacts.

14. The method of claim 13, wherein adding the one or more prerequisite build artifacts to the plurality of build artifacts comprises:

creating an augmented build artifact comprising a build artifact and the prerequisite build artifacts required to create the build artifact; and

adding the augmented build artifact to the plurality of build artifacts.

15. The method of claim 11, further comprising:

appending a bill of materials to the augmented binary file comprising data identifying each build artifact of the plurality of build artifacts; and

producing an output comprising the bill of materials from the received augmented binary file.

16. The method of claim 11, wherein the plurality of build artifacts are combined into an archive file, and the archive file is appended to the original binary file.

17. The method of claim 11, wherein each build artifact of the plurality of build artifacts has a type selected from the group consisting of:

source code file, source code directory structure, library file, build parameter, build script, system components, build machine configuration, and build machine image.

18. The method of claim 11, further comprising encrypting the plurality of build artifacts such that a decryption key is required to extract the plurality of build artifacts from the augmented binary file.

19. The method of claim 11, further comprising retrieving the plurality of build artifacts from one or more source code repositories.

20. The method of claim 11, further comprising appending an identification signature to the augmented binary file.

21. The method of claim 18, wherein the identification signature is recognizable by a software auditing tool.

12. A method for building a binary file including executable instructions, the method comprising:

identifying a plurality of build artifacts used to create an original binary file;

creating and storing an augmented binary file comprising the plurality of build artifacts appended to the original binary file, the augmented binary file having the same functionality when executed as the original binary file;

extracting the plurality of build artifacts from the augmented binary file; and

creating a new binary file with the extracted plurality of build artifacts.