在詹金斯构建Maven -SNAPSHOT项目

Question

I believe that the answer will be really easy, but I haven't figure out how to do it.

The problem is:

I have a third-party project, which is being cloned from github, so I'm not going to change anything there, but I need this project for my work with MUnit.

The project is mule-interceptor-module and it has a version 3.4-M4-SNAPSHOT.

I created a build in Jenkins and I want to get mule-interceptor-module-3.4-M4-SNAPSHOT.jar after it, but Jenkins REMOVES -SNAPSHOT from the jar name and updates pom.xml with new version: 3.4-M4 instead of 3.4-M4-SNAPSHOT . The project, which uses this one (munit) in its dependencies has 3.4-M4-SNAPSHOT. So I need the SNAPSHOT in version.

What I tried to do:

I tried to build the same project on the server, which my Jenkins is installed on, using just mvn clean install and I got mule-interceptor-module-3.4-M4-SNAPSHOT.jar.

The question is:

How to tune Jenkins so that I could finally have SNAPSHOT build?

My job setup:

• JDK: jdk 1.6.0_45

• Source Code Management:

  • Git
  • Repository URL: https://github.com/mulesoft/mule-interceptor-module.git
  • Branch Specifier (blank for default):3.4.x
  • Repository browser: githubweb
  • URL: https://github.com/mulesoft/mule-interceptor-module/

• Pre Steps:

  • Execute shell: git checkout 3.4.x
• Build:
  • Root POM: pom.xml
  • Goals and options: clean install
• Post steps:
  • Run regardless of build result
• Build Settings: - Publish Checkstyle analysis results - Publish FindBugs analysis results

Jenkins Console output Jenkins Console output wirh -X

The solution:

1. in Jenkins /Configuration/Build/Advanced check in Use private Maven repository
2. Choose Strategy: Local to the workspace
3. remove everything from /workspace folder by rm -R *

@Grove: thanks you a lot for the support!

Answer 1

I can see in the logs: Your branch is ahead of 'origin/3.4.x' by 1 commit. and Building Mule Interceptor Module 3.4-M4 . Could it be that your revision has 3.4-M4 as a version in the pom?

Answer 2

The solution:

• in Jenkins /Configuration/Build/Advanced check in Use private Maven repository
• Choose Strategy: Local to the workspace
• remove everything from /workspace folder by rm -R *

Answer 3

Why are using SNAPSHOT dependency from a 3rd party ? The standard is to use a RELEASE version, right ?

Answer Anyways the fact that using the private maven repository worked for you proves just one thing, that the negative cache in your server's maven repo was causing the problem. See this Q and A from me more than a year back, when exactly the same solution worked for me, albiet for a different problem and I marked it as the answer. Only to find a few months later that I did not go to the root cause of the problem and just found a workaorund.

To test this theory, set <updatepolicy> true <updatepolicy> and use maven -U clean install . It will have the same effect as your solution of using a private repo.