Automatic Build Queue Prioritization by Ticket Attributes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing program development systems lack efficient automatic execution processing capabilities, requiring manual settings and multiple configurations to handle varying priorities and attributes in continuous integration, such as ticket attributes like due dates and person in charge, leading to inefficiencies.
Innovation Solution
A program development assistance system with an automatic execution processing server that automatically adjusts processing based on ticket attributes, including priority, due dates, and person in charge, using modules to acquire, link, and change execution queue orders to optimize processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual settings are performed in advance for continuous integration tools and ticket management tools, then processing priority can be controlled, but the system complexity and time required for configuration increase
Solution Approach 1:
The system automatically determines execution priority by having the continuous integration tool itself extract ticket information and determine priority based on ticket attributes, eliminating the need for manual configuration of priority rules. The system serves itself by automatically linking tickets to build information and determining execution order without external intervention.
Solution Approach 2:
The continuous integration tool performs multiple functions: it manages build execution, extracts ticket information, determines execution priority, and controls the execution queue. This multi-functionality eliminates the need for separate configuration systems and reduces overall system complexity while maintaining ease of operation.
2Adaptability or versatility
If multiple preparation settings are made to handle various ticket attributes and situations, then all scenarios can be covered, but the setup time and complexity increase
Solution Approach 1:
The system dynamically determines execution priority based on ticket attributes at runtime rather than requiring static pre-configuration for all scenarios. The continuous integration tool flexibly adapts to different ticket types, priorities, and attributes by automatically extracting and evaluating ticket information when builds are queued.
Solution Approach 2:
The system changes the parameter of execution priority dynamically based on ticket attributes such as ticket type, priority level, and custom attributes. Instead of preparing multiple fixed configurations, the system adjusts execution parameters on-the-fly based on the specific ticket associated with each build.
3Productivity
If the number of commits increases, then more work can be processed, but automatic execution processing queues up and efficiency decreases
Solution Approach 1:
The system performs preliminary sorting of builds in the execution queue based on ticket priority attributes before execution begins. By pre-establishing the execution order based on ticket importance, the system ensures that high-priority builds are executed first without requiring manual intervention or causing delays, thus maintaining efficiency even with increased commit volume.
4Ease of manufacture
If simple linkage between tools is used, then integration is easy to implement, but automatic execution cannot be performed according to ticket content
Solution Approach 1:
The continuous integration tool acts as an intermediary that connects ticket management and build execution. It automatically extracts ticket information from the ticket management system and uses this information to control build execution priority and order, enabling automatic execution based on ticket content while maintaining simple tool integration.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
A program development assistance system including an automatic execution process server, wherein when the automatic execution process server accepts a commit completion notification indicating that a source code has been registered, commit information that includes source code information and ticket information is acquired, a ticket identifier is extracted from the commit information, attribute information pertaining to a ticket is acquired on the basis of the extracted ticket identifier, information to be executed that corresponds to the source code to be processed by automatic execution is stored in an automatic execution queue, the sequence of to-be-executed information in the automatic execution queue is altered on the basis of the acquired attribute information pertaining to the ticket, the source code and a test case that are to be processed by automatic execution are acquired, and an automatic execution process is performed using the source code and the test case on the basis of the sequence of to-be-executed information that has been altered by an automatic execution process alteration unit.