Natural language processing (NLP) enabled continuous integration and continuous delivery (CICD) deployment

1. A computing platform comprising: at least one processor; a communication interface communicatively coupled to the at least one processor; and memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to: configure a dependency knowledge graph indicating file dependencies for mainframe applications; configure an error knowledge graph indicating errors and corresponding solutions for the mainframe applications; receive mainframe source code; analyze, using the dependency knowledge graph and the error knowledge graph, the mainframe source code to identify potential errors and corresponding solutions; based on identifying an error in the mainframe source code, cause the mainframe source code to be updated according to the corresponding solution; analyze, using the dependency knowledge graph and the error knowledge graph, the updated mainframe source code to identify remaining errors; and based on identifying an absence of the remaining errors, send, to a mainframe build and deployment engine, the updated mainframe source code and one or more commands directing the mainframe build and deployment engine to execute a build process on the updated mainframe source code, wherein sending the one or more commands directing the mainframe build and deployment engine causes the mainframe build and deployment engine to automatically execute the build process.

2. The computing platform of claim 1, wherein configuring the dependency knowledge graph comprises communicating with a dependency data storage system to obtain the file dependencies for the mainframe applications.

3. The computing platform of claim 2, wherein configuring the dependency knowledge graph with the file dependencies for the mainframe applications copies the file dependencies to local storage at the computing platform.

4. The computing platform of claim 1, wherein configuring the error knowledge graph is based on historical error and solution information from historical mainframe application builds.

5. The computing platform of claim 1, wherein analyzing the mainframe source code to identify potential errors and corresponding solutions comprises: verifying, using the dependency knowledge graph, the presence of all necessary file dependencies and identifying, using the error knowledge graph, the presence of any historically identified error.

6. The computing platform of claim 1, wherein executing the mainframe build results in an error.

7. The computing platform of claim 6, wherein the memory stores additional computer readable instructions that, when executed by the at least one processor, cause the computing platform to: receive error information of the error; tokenize the error information; and update the dependency knowledge graph or the error knowledge graph based on the tokenized error information.

8. The computing platform of claim 1, wherein causing the mainframe source code to be updated comprises sending, to an enterprise computing device, an error notification indicating the corresponding solution.

9. The computing platform of claim 1, wherein causing the mainframe source code to be updated comprises automatically updating the mainframe source code based on the corresponding solution.

10. The computing platform of claim 9, wherein causing the mainframe source code to be automatically updated is based on identifying that a confidence score of the corresponding solution exceeds a predetermined confidence threshold.

11. A method comprising: at a computing platform comprising at least one processor, a communication interface, and memory: configuring a dependency knowledge graph indicating file dependencies for mainframe applications; configuring an error knowledge graph indicating errors and corresponding solutions for the mainframe applications; receiving mainframe source code; analyzing, using the dependency knowledge graph and the error knowledge graph, the mainframe source code to identify potential errors and corresponding solutions; based on identifying an error in the mainframe source code, causing the mainframe source code to be updated according to the corresponding solution; analyzing, using the dependency knowledge graph and the error knowledge graph, the updated mainframe source code to identify remaining errors; and based on identifying an absence of the remaining errors, sending, to a mainframe build and deployment engine, the updated mainframe source code and one or more commands directing the mainframe build and deployment engine to execute a build process on the updated mainframe source code, wherein sending the one or more commands directing the mainframe build and deployment engine causes the mainframe build and deployment engine to automatically execute the build process.

12. The method of claim 11, wherein configuring the dependency knowledge graph comprises communicating with a dependency data storage system to obtain the file dependencies for the mainframe applications.

13. The method of claim 12, wherein configuring the dependency knowledge graph with the file dependencies for the mainframe applications copies the file dependencies to local storage at the computing platform.

14. The method of claim 11, wherein configuring the error knowledge graph is based on historical error and solution information from historical mainframe application builds.

15. The method of claim 11, wherein analyzing the mainframe source code to identify potential errors and corresponding solutions comprises: verifying, using the dependency knowledge graph, the presence of all necessary file dependencies, and identifying, using the error knowledge graph, the presence of any historically identified error.

16. The method of claim 11, wherein executing the mainframe build results in an error.

17. The method of claim 16, further comprising: receiving error information of the error; tokenizing the error information; and updating the dependency knowledge graph or the error knowledge graph based on the tokenized error information.

18. The method of claim 11, wherein causing the mainframe source code to be updated comprises sending, to an enterprise computing device, an error notification indicating the corresponding solution.

19. The method of claim 11, wherein causing the mainframe source code to be updated comprises automatically updating the mainframe source code based on the corresponding solution.

20. One or more non-transitory computer-readable media storing instructions that, when executed by a computing platform comprising at least one processor, a communication interface, and memory, cause the computing platform to: configure a dependency knowledge graph indicating file dependencies for mainframe applications; configure an error knowledge graph indicating errors and corresponding solutions for the mainframe applications; receive mainframe source code; analyze, using the dependency knowledge graph and the error knowledge graph, the mainframe source code to identify potential errors and corresponding solutions; based on identifying an error in the mainframe source code, cause the mainframe source code to be updated according to the corresponding solution; analyze, using the dependency knowledge graph and the error knowledge graph, the updated mainframe source code to identify remaining errors; and based on identifying an absence of the remaining errors, send, to a mainframe build and deployment engine, the updated mainframe source code and one or more commands directing the mainframe build and deployment engine to execute a build process on the updated mainframe source code, wherein sending the one or more commands directing the mainframe build and deployment engine causes the mainframe build and deployment engine to automatically execute the build process.