Chained Build Triggering in Continuous Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing continuous integration build tools lack the ability to modify or configure running builds, requiring users to manually monitor and start subsequent builds after the completion of active builds, which is time-consuming and inefficient.
Innovation Solution
A user interface enhancement that allows users to select an active build and designate a job to be executed in response to its completion, enabling drag-and-drop operations to link jobs and stages dynamically, allowing for the execution of subsequent jobs based on the output parameters of the active build.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If users manually monitor and start subsequent builds after active build completion, then build execution can proceed, but time consumption and operational efficiency deteriorate
Solution Approach 1:
The system allows users to pre-configure job chaining relationships before builds execute. Users can drag and drop to associate subsequent jobs with active builds in advance, so that when the active build completes, the subsequent job automatically executes without requiring manual intervention. This preliminary configuration eliminates the need for manual monitoring and starting of subsequent builds.
2Adaptability or versatility
If build tools provide basic build execution capability, then builds can be performed, but the ability to modify or configure running builds deteriorates
Solution Approach 1:
The build workflow is segmented into discrete jobs that can be independently configured and executed. Each job represents a distinct build unit that can be chained to others through drag-and-drop associations. This segmentation allows the system to maintain basic build execution capability while adding configuration flexibility, as each job can be modified or reconfigured without affecting the entire build system.
Data Source
AI summary
The technology disclosed herein enables presenting, via a user interface, one or more builds, wherein each build comprises one or more first software build operations, and at least one first software build operation is currently executing, presenting, via the user interface, one or more computing jobs, wherein each job comprises one or more second software build operations, receiving, via the user interface, an input associating a job selected from the one or more jobs with a build selected from the one of the builds, and responsive to receiving the input, scheduling, execution of the second software build operations to occur in response to a completion of execution of the first software build operations. The input may be, for example, a drag-and-drop operation between the job and the build.