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
Unable to run commands with /bin/bash -c
in v19.12.0
#7557
Comments
Here's something rather strange, this fails (as detailed above)
However, this works just fine
Removing |
Can you share the agent logs from the time this task was failing? |
Is this what you're after, or is it the log on the agent itself?
|
No log on the agent itself. |
|
@bsodmike I was able to reproduce the issue. As part of performance improvement to our pipeline config pages we started utilizing the Pipeline Config API to update tasks as part of #7400 . <exec command="/bin/bash">
<arg>-c\r</arg>
<arg>echo $HOME</arg>
<runif status="passed" />
</exec> Since Now, the fix you mentioned was not due to removing the said line. It was because the whole config was overwritten by the arg without |
Unfortunately I did not find any \r sequences in the cruise-config.xml of our setup. For all of you needing a workaround I have found out this:
Not the best workaround for larger teams, but I hope it helps at least some people. |
The other workaround is to save the cruise_config.xml without making any changes.
|
There is another workaround but it will effect the performance of the pipeline config save page.
WARNING: This will revert the changes made for faster save of the pipeline configs (as it will make a full config save for every change). |
Verified on 20.1.0 (11055-ef4fcdcffd933ed6a319262c2ac112b6e56c7936) |
Issue Type
Summary
GoCD v19.12.0
Steps to Reproduce
Run a job with the following command
Expected Results
You should see the current path stored in the
$HOME
env var.Actual Results
The text was updated successfully, but these errors were encountered: