推荐阅读:
在一个多开发和生产环境的项目中,有dev、beta、prod等环境设置,如下:
pom.xml文件内容如下,指定plugins和profiles等:
<build>
<finalName>dlt-server</finalName>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.7</version>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
<!--使用下边的插件可以跳过测试test中的测试-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.7.1</version>
<configuration>
<skipTests>true</skipTests>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1.1</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>dev</id>
<build>
<resources>
<resource>
<directory>src/main/resources.dev</directory>
</resource>
<resource>
<directory>src/main/resources</directory>
</resource>
</resources>
</build>
</profile>
<profile>
<id>prod</id>
<build>
<resources>
<resource>
<directory>src/main/resources.prod</directory>
</resource>
<resource>
<directory>src/main/resources</directory>
</resource>
</resources>
</build>
</profile>
<profile>
<id>beta</id>
<build>
<resources>
<resource>
<directory>src/main/resources.beta</directory>
</resource>
<resource>
<directory>src/main/resources</directory>
</resource>
</resources>
</build>
</profile>
<profile>
<id>betb</id>
<build>
<resources>
<resource>
<directory>src/main/resources.betb</directory>
</resource>
<resource>
<directory>src/main/resources</directory>
</resource>
</resources>
</build>
</profile>
</profiles>
resource、resource.beat、resource.dev、resource.prod分别代表了不用环境的参数设置,我们在本地打包部署的时候,可以选择以下命令进行打包编译:
1、编译跳过测试:
mvn clean install -Dmaven.test.skip=true
2、部署到远程Nexus:
mvn deploy -Dmaven.test.skip=true
3、打包编译为不同的环境
mvn clean install -Pdev -Dmaven.test.skip=true
如果我们在使用Jenkins的时候不指定特定的参数的话,Jenkins默认只会根据resource
的环境参数进行编译打包,而对于特定环境dev、beta、prod这些环境变量并不会编译打包。
那么我们在使用Jenkins的时候如何设置这些参数,使得按着我们的想法去编译执行哪?答案如下:
在Jenkins ver. 2.46.1
下是这样设置的:
其中Goals and options
指定的就是以何种命令进行编译,注意的是这里是没有 ‘mvn’的,这一点在红色圈的位置也有说明,如果自己不知道加上了‘mvn’也就是参数为:
mvn clean install -Pdev -Dmaven.test.skip=true
就会报错:
[ERROR] Unknown lifecycle phase "mvn". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
因此,使用正确的参数之后就可以正确的编译了~