Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple machine runners and /tmp/SLACK_JOB_STATUS #475

Open
kozak opened this issue Mar 5, 2025 · 0 comments
Open

Multiple machine runners and /tmp/SLACK_JOB_STATUS #475

kozak opened this issue Mar 5, 2025 · 0 comments

Comments

@kozak
Copy link

kozak commented Mar 5, 2025

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:

  • runner-1
  • runner-2
  1. runner-1 has executed a workflow and failed
  2. runner-1 wrote the failed status /tmp/SLACK_JOB_STATUS
  3. runner-2 has executed a workflow and succeded
  4. runner-2 wrote the success status to /tmp/SLACK_JOB_STATUS
  5. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant