You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running a machine executor for our iOS builds and using multiple copies of it (an executor can process a job at a time).
This orb uses /tmp/SLACK_JOB_STATUS and some other /tmp/* files to pass information between jobs / commands.
It would be cool if the /tmp/SLACK_JOB_STATUS was namespaced so that multiple runners can coexist on the same machine.
Examples:
Say I have 2 instances of machine executor running:
runner-1
runner-2
runner-1 has executed a workflow and failed
runner-1 wrote the failed status /tmp/SLACK_JOB_STATUS
runner-2 has executed a workflow and succeded
runner-2 wrote the success status to /tmp/SLACK_JOB_STATUS
runner-1 has an incorrect job status
Another problem:
Say runner-1 and runner-2 are executed from different OS users (for isolation). There will be a permission problem with the shared /tmp/SLACK_JOB_STATUS file.
The text was updated successfully, but these errors were encountered:
Describe Request:
I am running a machine executor for our iOS builds and using multiple copies of it (an executor can process a job at a time).
This orb uses
/tmp/SLACK_JOB_STATUS
and some other/tmp/*
files to pass information between jobs / commands.It would be cool if the
/tmp/SLACK_JOB_STATUS
was namespaced so that multiple runners can coexist on the same machine.Examples:
Say I have 2 instances of machine executor running:
/tmp/SLACK_JOB_STATUS
/tmp/SLACK_JOB_STATUS
Another problem:
Say runner-1 and runner-2 are executed from different OS users (for isolation). There will be a permission problem with the shared
/tmp/SLACK_JOB_STATUS
file.The text was updated successfully, but these errors were encountered: