title: JFrog CLI can't set properties on an artifact in JFrog Artifactory for the first property name and using SSH key examples for multi property search
body: <p><strong>JFrog Artifactory:</strong> 5.8.4 Professional.</p>
  
  <p><strong>JFrog CLI:</strong> 1.12.1</p>
  
  <p>I'm using <a href="https://www.jfrog.com/confluence/display/CLI/CLI+for+JFrog+Artifactory" rel="nofollow noreferrer">the official documentation of JFrog CLI</a> to set few properties on an artifact that's available in Artifactory repo. </p>
  
  <ul>
  <li>NOTE: I don't want to use <code>Artifactory AQL</code> for now and trying to get this working using <code>jfrog</code> cli.</li>
  </ul>
  
  <p>I successfully configured the CLI client (the file <code>~/.jfrog/jfrog-cli.conf</code> with entries for authentication using either username/password and with an API Key was created successfully). </p>
  
  <p>For setting properties on an artifact, I referred the following example:</p>
  
  <pre><code>jfrog rt sp "generic-local/*.zip" "a=1;b=2,3"
  </code></pre>
  
  <p>and ran the following command (in a free-style Jenkins job):</p>
  
  <pre><code>$ jfrog rt sp --server-id="artifactory-dev-instance" --url=${ARTIFACTORY_URL} ${REPO}/${FILE_PATH}/${FILE_NAME} -- props="release=${RELEASE};VERSION=${VERSION};PIPELINE_VERSION=${RELEASE}_${VERSION}_${BUILD_NUMBER};fileType=automated-file;PROJECT=${PROJECT}"
  </code></pre>
  
  <p>This command exited successfully without giving an error and applied all the properties with expected values except the first property <code>release=${RELEASE}</code>.</p>
  
  <p><strong>Question:</strong> Why <code>jfrog rt sp</code> is not applying the <code>release</code> property on the artifact while all others properties got successfully applied with correct values.</p>
  
  <p>Actual variables values don't matter as I can see other properties getting applied successfully in the given Artifactory instance (ARTIFACTORY_URL), on the target file (sitting in a repo/path/file) and respective properties with their values.  </p>