convert service management plugin to jobs
Description
Problem/Justification
None
Impact
None
Activity
Show:
Caleb January 14, 2025 at 1:01 PM
yep, we should. I’ve changed it.
Vladimir Vinogradenko January 14, 2025 at 9:45 AM
should we punt this to 25.10? Since we’re not really releasing 25.04 as a stable API, it won’t be a problem.
Ievgen Stepanovych January 9, 2025 at 1:52 PM
Yes, it’s already using it.
I like the idea of jobs working differently, but I don’t know if we (as a department) have time to implement it. It’s less than 2 weeks before beta freeze.
Vladimir Vinogradenko January 9, 2025 at 9:02 AM
will UI be using JSON-RPC 2.0 in 25.04?
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Vladimir VinogradenkoReporter
CalebLabels
Fix versions
Affects versions
Priority
MediumMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created September 27, 2024 at 11:58 AM
Updated January 14, 2025 at 1:01 PM
We have an increasingly annoying problem where certain services will take > 60 seconds to startup. So we’re having to add hacky work-arounds so our middleware client doesn’t raise a CallTimeout (60 second default).
The docker service is one example, the directory services don’t have this problem but could in the future depending on what other integration we have.
Instead of adding these nasty hacks to work-around the default CallTimeout (or changing the call timeout to some arbitrary number), we should convert our service framework plugin to using jobs. This will be a rather large change (not necessarily in lines changed but for all upstream consumers). This will require changes to TrueConnect/TrueCommand/WebUI/our CI/CD and QE’s CI/CD environments.
We should also use a per-service lock so that we don’t have multiple threads/processes trying to start/stop/restart services in parallel.