Near-Real Time Code Deploy via File Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The traditional code deployment process is time-consuming and slows down the iterative development cycle, as it requires packaging and deploying code to a testing environment, which delays the reflection of changes made to source code in the destination directory tree.

Innovation Solution

An agent monitors designated files in the source file system at pre-determined intervals, synchronizing near-real time changes to corresponding locations in the destination file system, thereby avoiding the need for iterative packaging and deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional packaging and deployment process is used, then code changes are deployed to testing environment, but the process is time-consuming and slows down iterative development cycle

Engineering Contradiction:
Improvecode deployment accuracyVSAvoiditerative development cycle time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by monitoring file changes in real-time and automatically triggering deployment processes when changes are detected, eliminating the need for manual packaging and deployment steps. This preliminary automation resolves the contradiction by ensuring code changes are deployed accurately while significantly reducing the time required for iterative development cycles.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary monitoring system that acts as a mediator between the source code directory and the testing environment. This intermediary automatically detects file changes, determines which files need deployment, and orchestrates the transfer process, thereby maintaining deployment reliability while reducing manual intervention time and accelerating the iterative development cycle.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If manual packaging and deployment is performed, then code changes are reflected in destination directory tree, but the reflection is delayed and slows down testing process

Engineering Contradiction:
Improvecode change reflection accuracyVSAvoidtesting process speed
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The system implements continuous monitoring of the source code directory tree, maintaining an ongoing process that detects file changes as they occur. This continuous action ensures that code changes are reflected accurately in the destination directory while simultaneously improving testing process speed by eliminating delays associated with manual packaging and deployment cycles.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The patent employs a feedback mechanism where the monitoring system continuously checks for file changes and automatically triggers deployment when modifications are detected. This feedback loop ensures accurate reflection of code changes in the testing environment while improving productivity by reducing the time lag between code modification and testing availability.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If iterative packaging and deployment is required, then testing environment is updated, but the process complexity increases and slows down development iterations

Engineering Contradiction:
Improvetesting environment update capabilityVSAvoiddeployment process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements self-service by enabling automatic detection and deployment of code changes without requiring manual intervention. The monitoring system autonomously identifies modified files, determines deployment necessity, and executes the transfer process, thereby maintaining the ability to update the testing environment while significantly reducing process complexity and accelerating development iterations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

An intermediary automated system serves as a mediator between the source code and testing environment, replacing complex manual packaging and deployment processes. This intermediary handles all update operations automatically, preserving the testing environment's adaptability while reducing deployment process complexity and enabling faster development iterations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10019461B2Transparent and near-real time code deploys
Publication Date: 2018.07.10 CA TECH INC
  • US10019461B2 patent drawing
  • US10019461B2 patent drawing
  • US10019461B2 patent drawing

AI summary

A method includes monitoring a plurality of files in a source file system at pre-determined time intervals. The plurality of files in the source file system include a plurality of designated and undesignated files. The designated files are pre-selected for near-real time editing. Each of the plurality of files is stored at a respective source file path in the source file system. The method also includes detecting that one of the plurality of files in the source file system has been modified. The method further includes determining whether the modified file is a designated file. The method additionally includes, in response to determining that the modified file is a designated file, mapping the source file path of the modified file to a corresponding destination file path in a destination file system and copying the modified file from the source file path in the source file system to the destination file path in the destination file system.