No versions could be resolved for groupid.artifactid

I’m having an error while listing the Mavaen Repository Artifacts in my Jenkins server configuration. Error is given below.

No versions could be resolved for groupid.artifactid rtis.rtis_2.11

Error Message
But my Nexus server contains the available rtis versions correctly. My point is how I can retrieve those versions available in Nexus server to my Jenkins server?

  • jenkins notifying error occured in different steps by sending mail in Pipeline (former known as Workflow)
  • Adding a png image and table html while sending email in Jenkins
  • Algorithm negotiation fail SSH in Jenkins
  • Use xcodebuild (Xcode 8) and automatic signing in CI (Travis/Jenkins) environments
  • PowerMock PrepareForTest annotation causing problems with AmazonSQSClient constructor
  • Jenkins Grails plugin does not list lastest versions of Grails
  • Available versions in Nexus server
    Versions available in Nexus server

    Any help would be greatly appreciated.

    Thank You.

  • testUI (Jenkins) using espresso
  • Jenkins - Make heavy job wait for a certain number of executors to be available
  • How do I tag the current git changeset from inside the Jenkinsfile?
  • Jenkins Sonar Job aborted by anonymous. Weird job build behaviour
  • jenkins debugging of SCM
  • JSch session timeout limit
  • 3 Solutions collect form web for “No versions could be resolved for groupid.artifactid”

    As I figured out, automatically upadating mavan-metadata.xml file is the solution. In order to update the file, create a task sheduler for rebuild metadata with a cron job.
    Go to Administration -> Scheduled Tasks in Nexus Repo. For more info, please refer to the image given below.
    Cron job

    Jenkins is not finding nexus repository to resolve the artifact.

    Verify these settings are correct in Maven POM:


    Also, Jenkins plugin help page, will give you more information on what kind of settings you might be missing while setting up your job.

    You have to specify the type in the dependency to be downloaded. By default in Maven it is ‘jar’. However in your case it it ‘tgz’ so you have to specify that provided that is possible in the Jenkins user interface. I can not see that option but it should be there.

    The other potential problem is that is was flagged as not found in the local repository Jenkins is using. Then you would have to either delete the metadata or force an update of it. On the Maven commandline this would be done with -U however in your UI I am not sure.

    Git Baby is a git and github fan, let's start git clone.