System and method of automatic software release termination based on customized reporting static code analysis

1. A method of enforcing a deployment static code analysis comprising:

receiving, via a processor, human-readable code instructions for a customized software application;

compiling, via the processor, the human-readable code instructions into machine-executable code instructions;

performing, via the processor, a customized reporting static code analysis of the machine-executable code instructions to identify a critical code error resulting from violation of a pre-set customized rule associated with a pre-defined terminal risk;

receiving an instruction, via a network interface device, from a customer, to release, for execution, the machine-executable code instructions;

automatically terminating release of the machine-executable code instructions via the processor;

transmitting a notification to the customer identifying the pre-defined terminal risk, via the network interface device.

2. The method of claim 1 , wherein the customized software application is configured using a program object model (POM), and the human-readable code instructions are compiled into machine-executable code instructions based on the POM.

3. The method of claim 1 , wherein the pre-defined terminal risk is unpredictability of the machine-executable code instructions.

4. The method of claim 2 , wherein the pre-set customized rule bars the use of child class field names mirroring parent class field names within the machine-executable code instructions.

5. The method of claim 2 , wherein the pre-set customized rule bars the use of a forced exit method within the machine-executable code instructions.

6. The method of claim 2 , wherein the pre-set customized rule bars the use of infinite loops within the machine-executable code instructions.

7. The method of claim 2 , wherein the pre-set customized rule bars the use of a wait call, a notify call, or a notify all call on a thread instance within the machine-executable code instructions.

8. The method of claim 2 , wherein the pre-set customized rule bars a parent class within the machine-executable code instructions referencing a child class of the parent class during an initialization of a Java attribute defined by the parent class.

9. An information handling system operating a deployment static code analysis enforcement system comprising:

a processor receiving human-readable code instructions for a customized software application;

the processor compiling the human-readable code instructions into machine-executable code instructions;

the processor performing a customized reporting static code analysis of the machine-executable code instructions to identify a critical code error resulting from violation of a pre-set customized rule associated with a pre-defined terminal risk;

a network interface device receiving an instruction from a customer to release, for execution, the machine-executable code instructions;

the processor automatically terminating release of the machine-executable code instructions;

the network interface device transmitting a notification to the customer identifying the pre-defined terminal risk.

10. The information handling system of claim 9 , wherein the pre-defined terminal risk is instability of the machine-executable code instructions.

11. The information handling system of claim 10 , wherein the pre-set customized rule bars executing a wait call while a plurality of lock calls are executed within the machine-executable code instructions.

12. The information handling system of claim 10 , wherein the pre-set customized rule bars executing a thread.sleep call during execution of a lock call within the machine-executable code instructions.

13. The information handling system of claim 10 , wherein the pre-set customized rule bars the use of a wait call, a notify call, or a notify all call on a thread instance within the machine-executable code instructions.

14. An information handling system operating a deployment static code analysis enforcement system comprising:

a processor receiving human-readable code instructions for a customized software application and a program object model (POM);

the processor compiling the human-readable code instructions into machine-executable code instructions, based on the POM;

the processor performing a customized reporting static code analysis of the human-readable code instructions to identify a critical code error resulting from violation of a pre-set customized rule associated with a pre-defined terminal risk;

wherein the pre-defined terminal risk is non-scalability of the machine-executable code instructions;

a network interface device receiving an instruction from a customer to release, for execution, the machine-executable code instructions;

the processor automatically terminating deployment of the machine-executable code instructions;

the network interface device transmitting a notification to the customer identifying the pre-defined terminal risk.

15. The information handling system of claim 14 , wherein the pre-set customized rule bars executing a thread.sleep call during execution of a lock call within the machine-executable code instructions.

16. The information handling system of claim 14 , wherein the pre-set customized rule bars failure to close a connection, stream, file, or class within the machine-executable code instructions.

17. The information handling system of claim 14 , wherein the pre-set customized rule bars execution of a call to start a thread within a constructor for the machine-executable code instructions.

18. The information handling system of claim 14 further comprising:

the network interface device transmitting a notification to the customer identifying a class of the machine-executable code instructions at which the critical code error is identified.

19. The information handling system of claim 18 further comprising:

the network interface device transmitting a notification to the customer identifying a line of the class of the machine-executable code instructions at which the critical code error is identified.

20. The information handling system of claim 14 further comprising:

the network interface device transmitting a notification to the customer identifying a Java software tool executing the critical code error.