CI-CD Orchestration for Automated Pull Requests and Branch Deployment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Developers face challenges in effectively utilizing CI-CD pipeline tools due to a lack of automation, leading to inefficient branching strategies, manual cleanup of older feature branches, and manual generation of pull requests, which impacts productivity and software asset responsiveness and scalability.

Innovation Solution

A method and system for implementing orchestration of continuous integration and continuous deployment (CI-CD) that automates the creation of pull requests and code deployment, allowing minimal manual intervention by receiving user inputs through a developer utility platform, fetching project data, and generating pull requests without a code freeze request, and deploying changes between branches.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual processes are used for CI-CD activities (creating pull requests, cleaning branches, defining branching strategies), then developers have full control over each step, but productivity decreases and time consumption increases

Engineering Contradiction:

Improvedeveloper productivityVSAvoidautomation of CI-CD processes

Core Design Contradiction:

ProductivityVSExtent of automation

Solution Approach 1:

The system enables self-service automation where the CI-CD platform automatically performs pull request creation, branch cleanup, and deployment orchestration based on predefined rules and triggers, eliminating the need for manual developer intervention in routine tasks

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-configuring branching strategies, deployment pipelines, and automation rules before development cycles begin, allowing automated execution without real-time manual input while maintaining control

Inventive Principle:

Principle #10Preliminary action

2Loss of time

If manual cleanup of older feature branches is performed, then developers can manage branch lifecycle, but time and resources are significantly consumed

Engineering Contradiction:

Improvetime for branch cleanupVSAvoidmanual branch management

Core Design Contradiction:

Loss of timeVSEase of operation

Solution Approach 1:

The system implements self-service automated branch lifecycle management that automatically identifies, archives, and cleans up obsolete feature branches based on integration status and age criteria, eliminating manual cleanup efforts

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system continuously monitors branch status, integration progress, and usage patterns to provide feedback-driven automated decisions about which branches need cleanup, ensuring optimal resource management

Inventive Principle:

Principle #23Feedback

3Reliability

If branching strategies are manually configured, then developers can customize deployment paths, but errors occur such as direct merging to production without testing

Engineering Contradiction:

Improvedeployment reliabilityVSAvoidbranching strategy configuration

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system pre-configures validated branching strategies with enforced deployment paths and gating criteria before use, preventing configuration errors and ensuring reliable multi-stage deployment flows

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary automation layer that mediates between development branches and production, enforcing testing and approval gates to prevent direct unsafe merges while maintaining configurable flexibility

Inventive Principle:

Principle #24Intermediary (Mediator)

4Productivity

If multiple pull requests are created manually for code changes, then developers can review each change individually, but overall productivity is significantly impacted

Engineering Contradiction:

Improvepull request generation speedVSAvoidmanual pull request creation

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The system implements self-service automated pull request generation that automatically creates, submits, and tracks multiple pull requests based on code changes and predefined rules, dramatically increasing throughput

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system merges multiple individual pull request operations into a single automated workflow that handles batch creation, submission, and tracking, reducing manual effort while maintaining individual review capabilities

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS20260030007A1Method and system for implementing orchestration of continuous integration and continuous deployment

Publication Date: 2026.01.29 JPMORGAN CHASE BANK NA

AI summary

A system and method for implementing an orchestration of continuous integration and continuous deployment (CI-CD) are disclosed. The method includes receiving a set of data from at least one user to allow access to a developer utility platform and a request to access project data associated with at least one software product. The method includes fetching the project data from at least one database and displaying a plurality of options related to the project data. The method includes creating at least one pull request upon receiving input that relates to the plurality of options. The method includes generating the at least one pull request in case of an absence of a reception of a code freeze request. Next, the method includes implementing a deployment of a change in a code into a target branch from a source branch based on the generated at least one pull request.