Now that buildservice jobs are able to run in a nested way, we can handle them in the same way as regular jobs, and enable users to use filelogs for them.
This is more interesting for one-offs as the pods get removed and cleaned up after some time and then the users can't find the logs anymore.
Ideally, we would have the disabled by default for buildservice images, unless explictly specified, and enabled by default on the rest (current behavior).
But allow the user to force using them.
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| jobs-api: bump to 0.0.268-20240307140512-e8b5dd4d | repos/cloud/toolforge/toolforge-deploy!217 | project_1317_bot_df3177307bed93c3f34e421e26c86e38 | bump_jobs-api | main |
dcaro closed https://gitlab.wikimedia.org/repos/cloud/toolforge/jobs-cli/-/merge_requests/12
run: add filelog to buildservice if passed
dcaro merged https://gitlab.wikimedia.org/repos/cloud/toolforge/jobs-api/-/merge_requests/61
[command] wrap buildservice with a shell
project_1317_bot_df3177307bed93c3f34e421e26c86e38 opened https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/217
jobs-api: bump to 0.0.268-20240307140512-e8b5dd4d
dcaro merged https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/217
jobs-api: bump to 0.0.268-20240307140512-e8b5dd4d