US 11,853,735 B1
Systems and methods for continuous integration and continuous deployment pipeline management using pipeline-agnostic non-script rule sets
Tridib Choudhury, Kolkata (IN); Manish Shah, Flower Mound, TX (US); Satish Chandreskharan, Frisco, TX (US); Robert Kovach, Jersey City, NJ (US); Shweta Sobat, Frisco, TX (US); and Arunkumar Saripalli, Frisco, TX (US)
Assigned to Citibank, N.A., New York, NY (US)
Filed by Citibank, N.A., New York, NY (US)
Filed on Feb. 10, 2023, as Appl. No. 18/167,739.
Int. Cl. G06F 8/54 (2018.01); G06F 8/60 (2018.01); G06F 9/54 (2006.01); H04L 9/40 (2022.01); G06F 11/36 (2006.01); G06F 16/25 (2019.01)
CPC G06F 8/60 (2013.01) [G06F 9/54 (2013.01); H04L 63/0263 (2013.01); G06F 11/3664 (2013.01); G06F 11/3668 (2013.01); G06F 11/3672 (2013.01); G06F 16/254 (2019.01)] 18 Claims
OG exemplary drawing
 
1. A system for continuous integration and continuous deployment pipeline management using pipeline-agnostic rule sets applied to pre-deployment code samples, the system comprising:
one or more processors; and
a non-transitory, computer-readable medium comprising instructions that, when executed by the one or more processors, cause operations comprising:
receiving, via a first user interface, a first user input creating a first rule set for processing pre-deployment code samples, wherein the first user input is entered into a first field of a plurality of fields, wherein the pre-deployment code samples comprise commits to a pre-deployment codebase, and wherein the commits await testing prior to integration with a code repository of deployed code;
generating, using an application programming interface (API) suite, the first rule set based on the first user input, wherein the API detects data stream identifiers present in scripts of the pre-deployment code samples;
storing, in a rules engine, the first rule set, wherein the first rule set is archived with a plurality of rule sets, and wherein the rules engine applies the plurality of rules sets to the commits to the pre-deployment codebase that are awaiting testing prior to integration with the code repository of deployed code;
receiving, via a second user interface, a first request to process a first pre-deployment code sample;
determining, using the API suite, to use the first rule set to process the first pre-deployment code sample;
in response to the first request:
retrieving, based on the first rule set, a first source identifier indicating a first data source location for the first rule set; and
selecting, from a plurality of data streams at the first data source location, a first data stream based on the first data stream corresponding to a first data stream identifier included in script comprising the first pre-deployment code sample;
processing, using the API suite, the first pre-deployment code sample using the first rule set and the first data stream to determine whether the script comprising the first pre-deployment code sample meets a requirement of the first rule set; and
generating for display, on the second user interface, a first processing confirmation for the first pre-deployment code sample, wherein the first processing confirmation indicates that the script comprising the first pre-deployment code sample meets the requirement of the first rule set.