[jobs-api] buildservice-based jobs stopped prefixing the command with launcher
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	dcaro
	Aug 13 2025, 4:18 PM

Project Tags

Referenced Files

None

Subscribers

Description

We are not prepending the commands with launcher when it's a buildpack

Potential cause is jobs-api release 5fc586f098a81a6f2b366d060072ec563d404db1

Related Changes in GitLab:

	Title	Reference	Author	Source Branch	Dest Branch
	Revert "jobs-api: bump to 0.0.397-20250808001841-d9ce682d"	repos/cloud/toolforge/toolforge-deploy!919	dcaro	fix_launcher	main

Mentioned In: T403735: [jobs-api] use `launcher` also for health-check script commands
Mentioned Here: T401552: [logs-api,jobs-cli] `toolforge jobs logs` has inconsistent ordering

dcaro triaged this task as High priority.Aug 13 2025, 4:18 PM

dcaro updated the task description. (Show Details)

Revert "jobs-api: bump to 0.0.397-20250808001841-d9ce682d"

Mentioned in SAL (#wikimedia-cloud) [2025-08-13T16:23:54Z] <dcaro> reverting jobs-api release (T401846)

Mentioned in SAL (#wikimedia-cloud) [2025-08-13T16:36:31Z] <dcaro> reverting jobs-api release (T401846)

[jobs-api,builds-api] test for launcher str in buildpack image commands

Looking at the MR code it shouldn't double-prefix the command so I'll leave the jobs explicitly prefixed.

Draft: Test for launcher in buildpack image command

jobs-api: bump to 0.0.398-20250814013804-be4bd73d

dcaro closed this task as Resolved.Aug 14 2025, 9:05 AM