Centralized Build Module Policy Enforcement

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In software development, the current approach leads to code duplication and inefficiencies across projects, with developers unaware of platform updates, resulting in outdated build code and challenges in enforcing quality control across numerous applications.

Innovation Solution

A shared build module collects metrics across multiple projects, evaluates them against defined policies, and aborts the build process if these metrics do not comply, ensuring consistency and quality control by centralizing build code and enforcing policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers create their own build scripts for each project, then each project maintains independence and can be customized, but this leads to code duplication across projects and inefficient use of developer time

Engineering Contradiction:

Improveproject independenceVSAvoiddeveloper efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent merges build scripts from multiple projects into a centralized shared repository. The build module retrieves and executes these shared scripts, eliminating code duplication while maintaining project-specific customization through selective script inclusion. This resolves the contradiction by combining individual project needs with centralized code management.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The shared build script repository serves multiple projects simultaneously, making the build code universal across the enterprise. The build module acts as a multi-functional system that can retrieve, manage, and execute scripts for different projects, replacing the need for each project to maintain its own separate build scripts.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Stability of the object's composition

If build code is linked to a specific version of the software platform, then build processes are consistent with that platform version, but changes to the platform require modifications to build code and lead to gradual decay of build code quality

Engineering Contradiction:

Improvebuild process consistencyVSAvoidbuild code maintenance

Core Design Contradiction:

Stability of the object's compositionVSEase of manufacture

Solution Approach 1:

The build module implements feedback mechanisms by collecting metrics during build processes and evaluating them against policies. This feedback loop identifies when build code needs updates based on platform changes, enabling proactive maintenance rather than reactive modifications. The system monitors build health and triggers updates when degradation is detected.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by pre-evaluating build scripts against platform compatibility policies before execution. The build module checks scripts against current platform versions and identifies required modifications in advance, preventing build failures and reducing the need for urgent code changes when the platform evolves.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If the infrastructure manager wants to enforce quality control across numerous application projects, then consistency and quality standards are improved, but tracking and monitoring such data across high volumes of projects becomes challenging

Engineering Contradiction:

Improvequality controlVSAvoidtracking complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The build module serves as an intermediary between the infrastructure manager and numerous build processes. It centralizes the collection of build metrics from multiple projects and presents them in a unified format, simplifying the infrastructure manager's ability to enforce quality control policies across the enterprise without manually tracking each project individually.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system replaces manual tracking mechanisms with automated metric collection and evaluation. The build module automatically gathers build data, evaluates it against quality policies, and enforces standards through automated decisions, eliminating the need for complex manual monitoring systems and reducing tracking complexity.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11169902B2Techniques for evaluating collected build metrics during a software build process

Publication Date: 2021.11.09 INTUIT INC

AI summary

Techniques are disclosed for enforcing build policies for a software development project of a software platform. Metrics are collected during a stage in a build process for the software development project. The metrics are collected via a build module for building a software development project. The build module is common to software development projects of the software platform. Each of the metrics is evaluated against a plurality of policies. Each policy specifies one or more rules for whether to allow the build process to proceed. Upon determining that one of the metrics does not comply with at least one of a plurality of policies, the build process is aborted at the stage.