Jenkins uses "@" sign when creating new jenkins-pipeline workspace folders. The reason why these "@" are used is unclear for me, but I also don't need to understand how Jenkins works internally (although interesting...).
However, these "@" are causing us troubles because we are running bash commands from these workspace directories, and "@" is unfortunately not supported by some tools.
My question: is it possible to configure Jenkins so that it uses another sign than "@" for the workspace's path directories?
================
Ok, some additional research seem to mention than these "@" are used when concurrent build are possible. However, in our case, we explicitely checked the box mentioning that "no concurrent build are allowed".
(Sure we could take content of workspaces and copy them somwhere else in order to start our commands... but this can't be changed that easily ...)
@separator is hardcoded, so you either need to compile jenkins yourself or try to somehow work around these in your tooling (i.e. you are free to specify the workspace directory yourself, add some logic not containing@) – Dominik Gebhart