There are several plugins to do what you want.

A quick Google search returned me:

Build Number Maven Plugin

Just set up the plugin :

<plugins>
  <plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>buildnumber-maven-plugin</artifactId>
    <version>1.2</version>
    <executions>
      <execution>
        <phase>validate</phase>
        <goals>
          <goal>create</goal>
        </goals>
      </execution>
    </executions>
    <configuration>
      <doCheck>true</doCheck>
      <doUpdate>true</doUpdate>
    </configuration>
  </plugin>
</plugins>

That will feed the variable buildNumber .

<build>
   <finalName>${project.artifactId}-${project.version}-r${buildNumber}</finalName>
</build>

Maven SVN Revision Number Plugin

Same thing. Plugin configuration + prefix:

<plugin>
   <groupId>com.google.code.maven-svn-revision-number-plugin</groupId>
   <artifactId>svn-revision-number-maven-plugin</artifactId>
   <version>1.13</version> 
   <executions>
      <execution>
         <goals>
            <goal>revision</goal>
         </goals>
       </execution>
    </executions>
    <configuration>
       <entries>
          <entry>
             <prefix>prefix</prefix>
          </entry>
       </entries>
    </configuration>
</plugin>

And the revision number will be available in prefix.revision

<build>
   <finalName>${project.artifactId}-${project.version}-r${prefix.revision}</finalName>
</build>

In both cases it's also worth setting the SCM :

<scm>
    <connection>scm:svn:https://servidor/projeto/trunk</connection>
    <developerConnection>scm:svn:https://servidor/projeto/trunk</developerConnection>
    <tag>HEAD</tag>
    <url>https://servidor/projeto/trunk</url>
</scm>

Tip: Since you're taking time to automate the process, we recommend add the build version to Manifest . Placing the build number in the Manifest and storing a checksum of the generated artifact gives you confidence on the build version (just adding the version to the file name is good for cataloging, but does not guarantee much since the artifact can be renamed).

The simplest and "manual" way

The simplest practice for getting an artifact with the VCS revision of the file name is put the desired revision in the version set to pom.xml . Although it is a "manual" procedure, this helps to maintain some consistency.

Versions Maven Plugin can help with this task a little.

Using the releases plugin

There is also the Maven Release Plugin that could be useful depending on how your process. It is able to create a tag in SVN and update the version of the poms.

Changing the "final" name of the artifact in Maven

In Maven, you can set the <finalName> tag to its pom.xml so that after the build the final artifact has the name you want. See documentation here .

By default, maven adds the pom version as follows:

<finalName>${artifactId}-${version}</finalName>

Then you could define some other property, for example:

<finalName>${artifactId}-${revisao_svn}</finalName>

And Jenkins could be configured to pass the ${revisao_svn} parameter to Maven.

If you use a hook like the of this page

Finally, you just have to configure build parameters as explained this link . According to this answer this is perfectly possible.

Note : I currently do not have an environment to test all this, so unless someone gives you a more detailed solution, you'll have to uncover the details of the procedure.