Automated Script Deployment and Versioning System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack efficient mechanisms for automatically deploying and versioning scripts in a computing environment, leading to manual efforts, storage inefficiencies, and challenges in collaboration between developers and system administrators, with issues like code overrides, manual transaction management, and failure to detect syntax errors.

Innovation Solution

A computer-implemented method and system that validates scripts by executing them in a database, creates patch files, and automatically stores them in a repository server for versioning, sending notifications to authorized users, and maintaining a guidebook for each application, enabling automated deployment and versioning without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If scripts are manually managed and deployed, then developers have full control over the deployment process, but manual efforts increase and efficiency decreases

Engineering Contradiction:
Improvescript deployment efficiencyVSAvoidmanual effort time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system enables self-service automation where the deployment tool automatically validates scripts, generates patch files, versions them, and deploys them to databases without requiring manual intervention. The tool autonomously tracks script changes, manages versioning, and coordinates between developers and system administrators, eliminating the need for manual script management while maintaining full control over the deployment process.

Inventive Principle:
Principle #25Self-service

2Reliability

If all files in an application package are uploaded to the server during deployment, then complete application deployment is ensured, but storage space is wasted and deployment time increases

Engineering Contradiction:
Improvedeployment completenessVSAvoidstorage space
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The system extracts and identifies only the changed files within the application package by comparing the current package with the previously deployed version. Only these extracted changed files are then uploaded to the server, ensuring deployment completeness for updated components while eliminating the waste of storage space and time associated with uploading unchanged files.

Inventive Principle:
Principle #2Taking out (Extraction)

3Manufacturing precision

If scripts are executed and validated in the production database, then script accuracy is ensured, but database availability is affected and validation risks increase

Engineering Contradiction:
Improvescript validation accuracyVSAvoiddatabase availability
Core Design Contradiction:
Manufacturing precisionVSReliability

Solution Approach 1:

The system introduces an intermediary test database that mirrors the production database structure and data. Scripts are first validated by executing them in this isolated test environment, ensuring accuracy and detecting errors without affecting production database availability. Only after successful validation in the intermediary test database are the scripts deployed to the production database, eliminating validation risks to production systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of information

If version control is integrated with database objects, then script tracking is improved, but system complexity increases and integration challenges arise

Engineering Contradiction:
Improvescript version trackingVSAvoidsystem integration complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The deployment tool serves as a universal multi-functional system that integrates version control, script validation, patch file generation, and database deployment capabilities into a single platform. It automatically tracks script versions, manages versioning workflows, and coordinates between different systems without requiring separate specialized tools, thereby improving script tracking while avoiding the complexity of multiple integrated systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

5Adaptability or versatility

If developers and system administrators collaborate manually on deployment, then deployment requirements are customized, but collaboration time increases and coordination challenges arise

Engineering Contradiction:
Improvedeployment customizationVSAvoidcollaboration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system implements automated feedback loops where the deployment tool continuously monitors script changes, validates them, and communicates deployment status between developers and system administrators. The tool provides real-time feedback on validation results, deployment progress, and any issues encountered, enabling customized deployment workflows without requiring continuous manual coordination, thereby reducing collaboration time while maintaining adaptability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9836297B2Computer implemented method and system for automatically deploying and versioning scripts in a computing environment
Publication Date: 2017.12.05 TATA CONSULTANCY SERVICES LTD
  • US9836297B2 patent drawing
  • US9836297B2 patent drawing
  • US9836297B2 patent drawing

AI summary

Embodiments herein describe computer implemented methods and systems for automatically deploying and versioning scripts in a computing environment. One embodiment includes validating a plurality of scripts associated with an application stored in a repository server by executing the plurality of scripts in a first database, creating at least one patch file comprising at least one of the plurality of scripts upon successful validation of the plurality of scripts associated with the application, and automatically storing the at least one patch file in the repository server, where the at least one of the plurality of scripts are automatically versioned in the repository server. Further embodiments herein enable the plurality of users to track patch files by automatically storing the plurality of scripts with updated comments from the plurality of users. Further, a notification mechanism for alerting the plurality of authorized users about the change to the plurality of scripts is provided.