java - Why can't my tests see my system property when I release on Jenkins? -

I wrote some unit test code which is a system called "Jenkins_BUILD" Prints the value of the property. This property has a value when I run these commands locally:

  mvn --batch-mode test -DJENKINS_BUILD = true mvn test -DargLine = "- DJENKINS_BUILD = true" etc.  

But whatever I do, I can not get this property in my tests when I walk on Jenkins. This is the command line option that I am using:

  mvn -DargLine = "- DJENKINS_BUILD = true" --batch-mode -Dresume = false release: release: display  

is slightly different, but I do not know why this will happen. Why is System.getProperty ("JENKINS_BUILD") tap on Jenkins but is "true" in my local environment? Is there something to do with using : Prepare Release: Display ?

, but I'm not sure the difference is that he is trying to pass the debate in the release plugin, I'm trying to pass it to the definite fire plug-in. Also, I want to define the value in the command line without changing my pom.xml. Is there any way to do this?

FWW , the solution I does is linked to the job

Note that if you do not deduct your JVM, you will find the property set on the Maven command line; But, if you work for your JVM, then the property will have to be copied again into the JVM's argongoist list.

I'm feeling that you are stuck on some aspect of your construction but are not going to a new organline, or going through a new arginine, which is required from the Launch (Set) property Does not copy

This may mean that in order to make your organi configuration correct, in a default (empty) case where the argument is set and where the argument is not set. The second "example" in your link (Examples of Sander Wehrhagen) is giving details of it, even if this is not clear why.

As far as it is often encountered in Maven-release - plugin, keep in mind that during the Maven-release-plugin you have a "parent" Maven process that runs two full nested Maven Builds . Failure to pass arguments for children will mean that children will be run without the necessary arguments (as they are only logic for the original activity, not to run two Maven release versions and the next snapshot version.