Unable to transfer release 401

Contributing Infrastructure
3

That may indicate one of several possible issues, all related to the credentials associated with allowing the accelq Jenkins LDAP account (managed on accounts.jenkins.io) to upload releases of the ACCELQ CI-Connect plugin. Some of the possible causes include:

  • Wrong username in ~/.m2/settings.xml in the servers section for the repository maven.jenkins-ci.org. In your case, the username should be accelq since that is the Jenkins LDAP account that is allowed to upload releases of the ACCELQ CI-Connect plugin
  • Wrong password string in ~/.m2/settings.xml in the servers section for the repository maven.jenkins-ci.org. The instructions for generating the correct string are in “Artifactory credentials for Maven”

An example entry in ~/.m2/settings.xml might look like this:

  <servers>
    <server>
      <id>maven.jenkins-ci.org</id>
      <username>accelq</username>
      <!-- See https://www.jenkins.io/doc/developer/publishing/releasing-manually/#artifactory-credentials-for-maven -->
      <password>{yCdSXNtk04Al7T5BievxETW5Z6JB9Uxzc1+hPMX1JEheCY7DQabJ8sWO93Aizxng}</password>
    </server>
  </servers>

Note that the password I provided in that example is not the correct password for your account. The password I provided in that example is derived from randomly generated data unrelated to any Jenkins account.

Please be sure that you very carefully follow the instructions at:

You can test that the password is accepted without generating a new release by running the command mvn deploy while your repository is configured to deliver SNAPSHOT releases. That way you don’t “waste” releases while configuring your Jenkins LDAP credentials for the Jenkins artifact repository.