title: Using wildcard with symlink command creates wrong links when run from Jenkins
body: <p>I can't wrap my head around this issue. I run symlink command over SSH from my Jenkins job. In my Jenkins pipeline I have these 2 steps (among others).</p>
  
  <pre><code>sh "ssh ubuntu@${host} sudo ls -al /etc/nginx/sites-available"
  sh "ssh ubuntu@${host} sudo ln -sv /etc/nginx/sites-available/* /etc/nginx/sites-enabled/ -f"
  </code></pre>
  
  <p>Here's the relevant part of the log:</p>
  
  <pre><code>[Pipeline] sh
  [my_job] Running shell script
  + ssh ubuntu@XX.XX.XX.XX sudo ls -al /etc/nginx/sites-available
  total 12
  drwxr-xr-x 2 root   root   4096 Sep 18 17:27 .
  drwxr-xr-x 6 root   root   4096 Aug 30 12:27 ..
  -rw-r--r-- 1 ubuntu ubuntu  467 Sep 18 17:27 my-nginx-config
  [Pipeline] sh
  [my_job] Running shell script
  + ssh ubuntu@XX.XX.XX.XX sudo ln -sv /etc/nginx/sites-available/default /etc/nginx/sites-available/jenkins /etc/nginx/sites-enabled/ -f
  '/etc/nginx/sites-enabled/default' -&gt; '/etc/nginx/sites-available/default'
  '/etc/nginx/sites-enabled/jenkins' -&gt; '/etc/nginx/sites-available/jenkins'
  </code></pre>
  
  <p>Symlinks are created on my remote host but instead of the <code>my-nginx-config</code> symlink, the <code>default</code> and <code>jenkins</code> files (which are on my jenkins host at <code>/etc/nginx/sites-available</code>) are symlinked.</p>
  
  <p>If I don't use wildcard and run this, it works as expected:</p>
  
  <pre><code>sh "ssh ubuntu@${host} sudo ls -al /etc/nginx/sites-available"
  sh "ssh ubuntu@${host} sudo ln -sv /etc/nginx/sites-available/my-nginx-conf /etc/nginx/sites-enabled/ -f"
  </code></pre>