Hi,
I’m running a self-hosted instance of renovate-ce on Bitbucket Server.
I’m integrating with the renovate-ce API to fetch logs for Renovate jobs. When I request the logs of a running job, I receive a 404 HTTP error.
For example, I’m calling this endpoint:
GET /api/v1/repos/{org}/{repo}/-/jobs/{latest|jobId}
or
GET /system/v1/jobs/logs/{jobId}
Expected: Return the current logs of the running job.
Actual: 404 Not Found until the job finishes.
Is this behavior expected?
If it’s intentional, are there plans to improve this API so that logs for running jobs can be streamed or retrieved? I’d be interested in contributing if there’s a roadmap or a specific direction to follow.
Thanks!
Thibaut.
Hi,
I’m running a self-hosted instance of renovate-ce on Bitbucket Server.
I’m integrating with the renovate-ce API to fetch logs for Renovate jobs. When I request the logs of a running job, I receive a 404 HTTP error.
For example, I’m calling this endpoint:
GET /api/v1/repos/{org}/{repo}/-/jobs/{latest|jobId}
or
GET /system/v1/jobs/logs/{jobId}
Expected: Return the current logs of the running job.
Actual: 404 Not Found until the job finishes.
Is this behavior expected?
If it’s intentional, are there plans to improve this API so that logs for running jobs can be streamed or retrieved? I’d be interested in contributing if there’s a roadmap or a specific direction to follow.
Thanks!
Thibaut.