trTryGhost
GitHubGhostWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionFailed
      troy-ny-1558-addendum-admin
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    Changed the Tinybird sync cadence back to every five minutes ref https://linear.app/ghost/issue/NY-1559 The job was moved to a 20-second cadence for local development so a change in the automation tables showed up in Tinybird quickly. That cadence is far more than the stats need, and it removed all slack from the pipeline: a run that failed was retried 20 seconds later with no backoff, and a run that outlasted the interval meant the next tick attached to it immediately, so any backlog was sent as one continuous stream. Five minutes is the cadence the job was designed for, matches the other recurring maintenance jobs, and is a natural retry delay after a failed run. The random per-process offset stays so sites do not all run at once.
    nx run-many --target=build --projects=tag:public-app
Succeeded
Linux
4 CPU cores
read-write access token used
9bedc1ab30560
100%

Cache hits

6 of 6 tasks used cache.

Protect cache integrity with sandboxing

Get faster results

Learn how to enable distribution.

Atomizer enabled

6 groups of tasks optimized.

See resource usage for your runs

Add the resource usage add-on to record CPU and memory per task on your run's main agent and trace slow runs or out-of-memory failures to the task that caused them.

Add resource usage

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubGhostWorkspace