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
Is your feature request related to a problem? Please describe
I'd like to run a task / cmd in the background, allowing the next task / cmd to run, making use of what's been started by the first task / cmd.
My use case is in uds-engine we are embedding the ui in a Go backend. For e2e testing running in CI, we want to start the backend and then execute the npm script that runs our playwright tests, which will run against that Go server.
The task:
The current issue is that even when using the & at the end of our server cmd Maru does not move on to the next cmd in the sequence.
At the moment, the only way to do this is to split the task into 2 separate tasks and call them from two different terminals.
Describe the solution you'd like
Given a single task that has cmds with & (or some other designation)
When those cmds are processed they run in the background
Then the next cmd / task runs
Describe alternatives you've considered
Potentially #80 could solve this issue as well, allowing us to call both tasks, to start the backend and run the tests, from a single point in our CI workflow.
e.g.
- name: Run server and then e2e testsrun: uds run test:e2e-backend test:e2e-frontend
Another workaround (that we're currently doing) is to remove the server startup from a task and run it directly in a github actions step because github actions handles the background cmd and moves on to the next step
# Run e2e backend first to start air server in the background
- name: Run e2e backend setuprun: | uds run setup:slim-cluster --no-progress go install github.com/air-verse/air@latest air -c .air.toml &
- name: Run e2e frontend testsrun: uds run test:e2e --no-progress
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
I'd like to run a task / cmd in the background, allowing the next task / cmd to run, making use of what's been started by the first task / cmd.
My use case is in uds-engine we are embedding the ui in a Go backend. For e2e testing running in CI, we want to start the backend and then execute the npm script that runs our playwright tests, which will run against that Go server.
The task:
The current issue is that even when using the
&
at the end of our server cmd Maru does not move on to the next cmd in the sequence.At the moment, the only way to do this is to split the task into 2 separate tasks and call them from two different terminals.
Describe the solution you'd like
&
(or some other designation)Describe alternatives you've considered
Potentially #80 could solve this issue as well, allowing us to call both tasks, to start the backend and run the tests, from a single point in our CI workflow.
e.g.
Another workaround (that we're currently doing) is to remove the server startup from a task and run it directly in a github actions step because github actions handles the background cmd and moves on to the next step
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: