It looks like the "sh" step uses the same shell session that the Jenkins
agent does when connecting a node to master. Therefore, any default shell
configuration is determined in node settings, and changing it, or any of
the dot files, requires reconnecting the node to reload them.
I would say i
I'm experiencing a similar issue, did you find a solution?
On Wednesday, 9 January 2019 09:19:25 UTC, Kamil Dzierżanowski wrote:
>
> Hello,
>
> I'm trying to determine, which (if any) files are sourced by the shell, in
> which commands specified in "sh" pipeline step are executed. I need to make
On Wednesday, 9 January 2019 09:19:25 UTC, Kamil Dzierżanowski wrote:
>
> Hello,
>
> I'm trying to determine, which (if any) files are sourced by the shell, in
> which commands specified in "sh" pipeline step are executed. I need to make
> sure the NVM (Node Version Manager) is sourced everytim
Hello,
I'm trying to determine, which (if any) files are sourced by the shell, in
which commands specified in "sh" pipeline step are executed. I need to make
sure the NVM (Node Version Manager) is sourced everytime this step is used.
I tried numerous dot-files for the user the Jenkins agent is u
