Resolve BuildScriptExecutor Errors During Process Import with Multiple Custom Script Executors #6256
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses BuildScriptExecutor errors encountered when importing a process containing multiple custom script executors. The issue stemmed from building the imported script executors simultaneously, leading to Docker errors such as
error 137
and the/generator container already running
error upon the second attempt to build the script executor.The solution involves implementing Laravel's WithoutOverlapping middleware to the BuildScriptExecutor Job. This middleware prevents jobs from overlapping and ensures they run consecutively, resolving the errors encountered during the process import.
Solution
How to Test
Import the provided process template containing multiple custom script executors.
Test_Template.json.txt
Create a new process from the imported template.
Monitor the Admin -> Queue Management for Pending, Completed, and Failed Jobs.
Verify that the BuildScriptExecutor job successfully completes without errors.
Related Tickets & Packages
ci:next
Code Review Checklist