测试开发技术网站

[【原文链接】GitLabCICD发布jar包到基于nexus的私有maven源仓库](http://devops-dev.com/article/407)

[TOC]
# 一、配置maven的配置文件
在GitlabCICD流水线中，可以通过执行mvn deploy 命令将jar包发布到nexus服务仓库，在发布之前，首先需要在maven的配置文件中配置一下nexus服务器的信息，但在GitlabCICD中修改maven配置文件是非常麻烦的，此时可以借助 mvn deploy -s xxx.xml指定新的配置文件的方式，因此这里需要在代码仓根目录增加一个maven的配置文件，比如 maven_deploy_setting.xml，只需要在配置文件中配置一下server即可，即如下内容，id随意设置，然后设置nexus的用户名和密码：

```xml
        <server>
            <id>nexus</id>
            <username>admin</username>
            <password>xxxxxxxx</password>
        </server>
```
全部内容如下，即在模板文件中增加了以上server的配置：
```xml
<?xml version="1.0" encoding="UTF-8"?>

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">

<pluginGroups>
        
    </pluginGroups>

<proxies>
        
    </proxies>

<servers>
        
        <server>
            <id>nexus</id>
            <username>admin</username>
            <password>xxxxxxxx</password>
        </server>
        
    </servers>

<mirrors>
        
    </mirrors>

<profiles>
        <!-- profile
         | Specifies a set of introductions to the build process, to be activated using one or more of the
         | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
         | or the command line, profiles have to have an ID that is unique.
         |
         | An encouraged best practice for profile identification is to use a consistent naming convention
         | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
         | This will make it more intuitive to understand what the set of introduced profiles is attempting
         | to accomplish, particularly when you only have a list of profile id's for debug.
         |
         | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
        <profile>
          <id>jdk-1.4</id>

<repositories>
            <repository>
              <id>jdk14</id>
              <name>Repository for JDK 1.4 builds</name>
              <url>http://www.myhost.com/maven/jdk14</url>
              <layout>default</layout>
              <snapshotPolicy>always</snapshotPolicy>
            </repository>
          </repositories>
        </profile>
        -->

<!--
         | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
         | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
         | might hypothetically look like:
         |
         | ...
         | <plugin>
         |   <groupId>org.myco.myplugins</groupId>
         |   <artifactId>myplugin</artifactId>
         |
         |   <configuration>
         |     <tomcatLocation>${tomcatPath}</tomcatLocation>
         |   </configuration>
         | </plugin>
         | ...
         |
         | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
         |       anything, you could just leave off the <value/> inside the activation-property.
         |
        <profile>
          <id>env-dev</id>

<activation>
            <property>
              <name>target-env</name>
              <value>dev</value>
            </property>
          </activation>

<properties>
            <tomcatPath>/path/to/tomcat/instance</tomcatPath>
          </properties>
        </profile>
        -->
    </profiles>

</settings>

```

# 二、配置pom.xml文件
（1）如下，首先拷贝要上传的仓库的url
![](https://redrose2100.oss-cn-hangzhou.aliyuncs.com/img/5a1816b6-487a-11ed-8df2-0242ac110002.png)

（2）然后在项目的pom.xml文件中的project标签下增加如下内容，这里的id需要和步骤一中的maven配置的id保持一致

```xml
    <distributionManagement>
        <repository>
            <id>nexus</id>
            <url>https://xxx.xxx.com/repository/maven-osssc</url>
        </repository>
    </distributionManagement>
```

# 三、编写 .gitlab-ci.yml 文件
如下：
* only：指定只有当gitlab代码仓打tag时才执行
* when: manual 指定了当打tag后手动触发
* mvn versions:set -DnewVersion=${CI_COMMIT_TAG} 命令是将jar的版本号设置为gitlab代码仓打的tag值
* mvn clean deploy -Dmaven.test.skip=true -s maven_deploy_setting.xml 忽略测试并且指定maven配置文件为当前目录下的maven_deploy_setting.xml文件，即步骤一中编写的maven的配置文件

```yaml
stages:
  - release

release :
  when: manual
  image: maven:3.8.5-openjdk-8
  stage: release
  script:
    - mvn clean
    - mvn versions:set -DnewVersion=${CI_COMMIT_TAG}
    - mvn clean deploy -Dmaven.test.skip=true -s maven_deploy_setting.xml
  only:
    - tags
  tags:
    - docker_in_docker
```

# 四、执行验证
（1）在gitlab上打0.0.4的tag
![](https://redrose2100.oss-cn-hangzhou.aliyuncs.com/img/e8580f66-487b-11ed-8df2-0242ac110002.png)

（2）gitlab的流水线中出现如下按钮，点击即可执行
![](https://redrose2100.oss-cn-hangzhou.aliyuncs.com/img/1eebdaf8-487c-11ed-8df2-0242ac110002.png)

（3）执行完成后，在nexus对应的仓库上已经存在0.0.4的版本的jar包了
![](https://redrose2100.oss-cn-hangzhou.aliyuncs.com/img/aa1345ee-487c-11ed-8df2-0242ac110002.png)

测试开发技术网站

博客