|
|
Deploy self-hosted Kura cache nodes bridged to the managed mesh
Enterprise accounts can now run their own Kura cache nodes inside their own infrastructure while staying connected to the same mutually auth
|
Kura, Tuist
|
Kura
|
xcresult-processor-image@0.31.0
|
GitHub
|
|
|
Stranded runner jobs are now automatically cleared from the queue
Runner jobs that get stuck in the queued phase no longer remain visible as queued indefinitely. The system now periodically reconciles these
|
Tuist
|
Compute
|
xcresult-processor-image@0.31.0
|
GitHub
|
|
|
Self-hosted Kura cache nodes with per-account mesh CA enrollment
You can now run your own Kura cache nodes in your own infrastructure, enrolled into the same mutually authenticated mesh as your Tuist-manag
|
Kura, Tuist
|
Kura
|
helm@0.11.0
|
GitHub
|
|
|
Self-hosted Kura cache nodes with per-account mesh CA enrollment
You can now run Kura cache nodes in your own infrastructure while keeping them enrolled in the same mutually authenticated mesh as Tuist-man
|
Kura, Tuist
|
Kura
|
helm@0.11.0
|
GitHub
|
|
|
Automatic recovery for runner jobs stuck in the queued phase
Tuist Server now runs a new worker that cleans up runner jobs left stranded in the queued phase. It cross-checks GitHub to reconcile missed
|
Tuist
|
Compute
|
server@1.220.0
|
GitHub
|
|
|
Self-hosted Kura cache nodes with per-account mesh isolation
Customers can now run their own Kura cache nodes inside their own infrastructure while staying connected to the same mutually authenticated
|
Kura, Tuist
|
Kura
|
server@1.220.0
|
GitHub
|
|
|
Self-hosted Kura cache nodes with per-account CA enrollment
Organizations can now deploy self-hosted Kura cache nodes on their own infrastructure and have them authorized by Tuist's control plane. Eac
|
Kura, Tuist
|
Kura
|
server@1.220.0
|
GitHub
|
|
|
Stuck queued runner jobs are now automatically recovered
Runner jobs that become stranded in the queued phase are now automatically recovered. A new background worker periodically cross-checks stal
|
Tuist
|
Compute
|
server@1.220.0
|
GitHub
|
|
|
Suite-level test sharding now uses accurate, module-qualified historical timing
Fixed a bug in suite-level test sharding where every suite was assigned the same median duration, causing all suites to collapse into a sing
|
Tuist
|
Compute
|
xcresult-processor-image@0.30.3
|
GitHub
|
|
|
Fixed suite-level sharding collapsing to a single shard
Suite-granularity sharding now correctly matches historical test timing using module-qualified names (Module/Suite). Previously, the server
|
Tuist
|
Compute
|
xcresult-processor-image@0.30.3
|
GitHub
|
Hive