Web Publishing Pipeline Segmentation for Deployment Accuracy

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The process of deploying a Web application on a Web server is time-consuming and prone to errors due to the complexity of copying files, making configuration changes, troubleshooting, and iterating through these steps until the production server is correctly configured.

Innovation Solution

A publishing pipeline with multiple segments is introduced, where file data is collected, necessary settings are determined, and transformation actions occur to prepare files for publication, simplifying the deployment process by collecting, transforming, and outputting the necessary files and settings to the target environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual deployment process is used (copying files, making configuration changes, troubleshooting), then the Web application can be deployed to the Web server, but the process consumes a great deal of time and energy and is prone to errors

Engineering Contradiction:

Improvedeployment accuracyVSAvoiddeployment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The deployment process is divided into distinct segments or phases: file collection, settings determination, transformation actions, and publication. Each segment handles specific tasks independently, allowing for systematic processing and reducing errors associated with manual, monolithic deployment procedures.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Files and settings are collected and prepared in advance before the actual deployment. Transformation actions are determined beforehand, and only then is the publication executed. This preliminary preparation reduces deployment time and ensures accuracy by preventing last-minute errors.

Inventive Principle:

Principle #10Preliminary action

2Reliability

Engineering Contradiction:

Improvedeployment accuracyVSAvoiddeployment process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The complex deployment process is segmented into manageable phases: collecting file data, determining settings, performing transformation actions, and publishing. This segmentation reduces perceived complexity and makes the process more systematic and less frustrating.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary publishing pipeline that mediates between the source environment and target environment. This pipeline automatically handles file collection, transformation, and publication, reducing the complexity of direct manual deployment operations.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If iterative deployment process is used (copying files, making configuration changes, attempting to run, troubleshooting errors), then the Web server can be configured, but the process consumes a great deal of time and energy

Engineering Contradiction:

Improvedeployment easeVSAvoiddeployment efficiency

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

All necessary files are collected and all transformation actions are determined before the publication step. This preliminary action eliminates the need for iterative troubleshooting and re-deployment, significantly improving deployment efficiency while maintaining ease of operation through automated processes.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system determines settings that need to be created or changed in the target environment based on analysis of the source environment and deployment requirements. This feedback mechanism ensures correct configuration on first attempt, eliminating iterative retry cycles and improving productivity.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS8892701B2Web publishing pipeline

Publication Date: 2014.11.18 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Aspects of the subject matter described herein relate to publishing applications from a source environment to a target environment. In aspects, a publishing pipeline has multiple segments in which work related to the publishing is performed. In the pipeline, file data associated with an application is collected. Settings that need to be created and/or changed in target environment are also determined. Transformation actions may also occur to determine and prepare files to be published to the target environment. After the files and settings to publish are determined and the transformation actions occur, the application may then be published to the target environment.