Jenkins Maven Nexus，如何学习？

Question

TASK: I was charged to make/test CI pipeline for any Java (Maven preferably) sources in Jenkins (all Devops tools must be in Docker containers) . I need to do basic stages :

• 1) Get source from github - done (I did by creating task in Jenkins and used example java app from some github repo)

• 2) Build in Maven - done

• 3) Make Junit tests - done

• 4) Push artifacts ( .war file probably) to Nexus 3 repository - need to solve

HOW I tried to SOLVE: I've found the docker-ci-tool-stack ( "Devops-ready" platform: Jenkins, SonarQube, Nexus, GitLab) , so I've just used it for my purpose (here it is https://github.com/marcelbirkner/docker-ci-tool-stack ) First I've tried to understand building app example from that repo, but stuck in Groove DSL scripts. After I've been trying look some tutorials, documents on integration: Jenkins , Maven and Nexus, but it's incomprehensible for me. I agree, that I should own each tool separately and after combine it together (and work in other place probably) , but I've a terms from by boss... What should I do? I passed some courses in Linux Academy for Git, Docker and Jenkins, but I still feel really raw in practice that DevOps (CI/CD), Thank you.

Answer 1

Well you can try other way. which i can say non maven way and it is like using nexus artifact uploader plugin . If you are use jenkins pipeline then there step for it in syntax generator. Refer the images

here groupid and version can be any value i chose this random values in repository pass the name of repo that you created in nexus dashboard wH.png artifactid and classifier can be any value. in the type write war if its war file , jar if its jar or zip if its zip file; Then in File section pass the path of war file which was created after creating the build When you click generate buld you will get this step script just paste it after the step where war file has been build

Answer 2

You can do this by adding the distributionManagement section to your pom.xml file.

<project ...>

  ...

  <distributionManagement>
    <snapshotRepository>
      <id>nexus-snapshots</id>
      <url>http://your-host:8081/repository/maven-snapshots/</url>
    </snapshotRepository>
    <repository>
      <id>nexus-releases</id>
      <url>http://your-host:8081/repository/maven-releases/</url>
    </repository>
  </distributionManagement>
</project>

And add in Jenkins job to Maven(mvn) section:

deploy

Briefly:

• Infrastructure with maven, Jenkins, Nexus

More details here:

• http://www.sonatype.org/nexus/2017/02/08/using-nexus-3-as-your-repository-part-1-maven-artifacts/

• http://www.baeldung.com/maven-deploy-nexus