Reliability
What happens if Trunk is slow or down?
What happens if Trunk is slow or down?
Every job runs. The action is built to retry for resiliency, but if Trunk is
down, the action will fail open and all your jobs will run.
What happens to a job Trunk has never seen?
What happens to a job Trunk has never seen?
It runs. A job needs a couple of days of history before Trunk will
recommend skipping it.
Can Dynamic CI skip a job in my merge queue?
Can Dynamic CI skip a job in my merge queue?
Only when a paths filter you configured excludes it. See
Merge queues.
Can I make sure a skipped job runs before a pull request enters the queue?
Can I make sure a skipped job runs before a pull request enters the queue?
Yes. Set the job to Run Before Queue.
Trunk starts it on the head commit before the pull request enters the
queue, unless it already ran there.
Why is my pull request held with a Run Before Queue line?
Why is my pull request held with a Run Before Queue line?
Trunk is starting its Run Before Queue jobs on the head commit. If the
line says Run Before Queue failed to start, force the jobs and rerun,
or push. See Failed to start.
Forks
What happens on pull requests from forks?
What happens on pull requests from forks?
A pull request from a fork has no access to your repository’s secrets, so
the filter job has no token and every job runs.
Does Run Before Queue work on pull requests from forks?
Does Run Before Queue work on pull requests from forks?
No. Dynamic CI runs every job on them.