之前挖了不少開源專案的坑 ,準備慢慢填起來 .第一步當然從專案管理開始 ,把之前的maven專案弄得更加規整.

Maven

還是延續之前的parent-pom/child-jar的結構
* parent中只留配置 : dependencies/plugins 都替換成 management節點
* 補充scm/issue等節點資訊 ,供其他工具整合
* 增加source/javadoc等plugin ,方便第三方使用者使用.
* 增加程式碼掃描工具(最好是通過IDEA的編寫時工具檢測更好)

<?xml version="1.0" encoding="UTF-8"?>
<project
 
 xmlns="http://maven.apache.org/POM/4.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>site.koalazoo.cutekoala</groupId>
  <artifactId>
 
cute-koala</artifactId>
  <version>0.1.0</version>
  <packaging>pom</packaging>

  <name>Cute Koala</name>
  <url>https://github.com/Anddd7/cute-koala</url>
  <description>Manage your Java Application easiler.</description>

  <licenses>
    <license
 
>
      <name>Apache License, Version 2.0</name>
      <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
      <distribution>repo</distribution>
    </license>
  </licenses>

  <issueManagement>
    <system>GitHub Issues</system>
    <url>https://github.com/Anddd7/cute-koala/issues</url>
  </issueManagement>

  <inceptionYear>2017</inceptionYear>

  <scm>
    <connection>scm:git:https://github.com/Anddd7/cute-koala.git</connection>
    <developerConnection>scm:git:[email protected]:Anddd7/cute-koala.git</developerConnection>
    <url>https://github.com/Anddd7/cute-koala</url>
  </scm>

  <developers>
    <developer>
      <id>and777</id>
      <name>Eddy Liao</name>
      <email>[email protected]</email>
      <roles>
        <role>owner</role>
        <role>developer</role>
      </roles>
      <timezone>+8</timezone>
    </developer>
  </developers>

  <modules>
    <module>koala-core</module>
    <module>koala-test</module>
  </modules>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <project.build.jdk.v>1.8</project.build.jdk.v>

    <junit.v>4.12</junit.v>
    <slf4j-log4j12.v>1.7.5</slf4j-log4j12.v>
    <lombok.v>1.16.18</lombok.v>
    <fastjson.v>1.2.33</fastjson.v>
    <mysql-jdbc.v>6.0.6</mysql-jdbc.v>
    <guava.v>22.0</guava.v>
    <beetl.v>2.7.16</beetl.v>
    <snakeyaml.v>1.18</snakeyaml.v>
  </properties>

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.slf4j</groupId>
        <artifactId>slf4j-log4j12</artifactId>
        <version>${slf4j-log4j12.v}</version>
      </dependency>

      <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <version>${junit.v}</version>
        <scope>test</scope>
      </dependency>

      <dependency>
        <groupId>org.projectlombok</groupId>
        <artifactId>lombok</artifactId>
        <version>${lombok.v}</version>
        <scope>provided</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>

  <build>

    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>3.6.1</version>
        <configuration>
          <source>${project.build.jdk.v}</source>
          <target>${project.build.jdk.v}</target>
        </configuration>
      </plugin>
    </plugins>

    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-source-plugin</artifactId>
          <version>2.1.2</version>
          <executions>
            <execution>
              <id>attach-sources</id>
              <goals>
                <goal>jar-no-fork</goal>
              </goals>
            </execution>
          </executions>
        </plugin>

        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-javadoc-plugin</artifactId>
          <version>2.10.4</version>
          <configuration>
            <quiet>true</quiet>
            <notimestamp>true</notimestamp>
            <additionalparam>-Xdoclint:-html</additionalparam>
            <encoding>${project.build.sourceEncoding}</encoding>
            <docencoding>${project.build.sourceEncoding}</docencoding>
            <charset>${project.build.sourceEncoding}</charset>
            <additionalparam>-XDignore.symbol.file</additionalparam>
            <additionalparam>-Xdoclint:-html</additionalparam>
            <linksource>true</linksource>
          </configuration>
          <executions>
            <execution>
              <id>attach-javadocs</id>
              <goals>
                <goal>jar</goal>
              </goals>
            </execution>
          </executions>
        </plugin>

        <plugin>
          <groupId>org.projectlombok</groupId>
          <artifactId>lombok-maven-plugin</artifactId>
          <version>1.16.18.1</version>
          <executions>
            <execution>
              <phase>generate-sources</phase>
              <goals>
                <goal>delombok</goal>
              </goals>
            </execution>
          </executions>
        </plugin>

        <plugin>
          <groupId>org.jacoco</groupId>
          <artifactId>jacoco-maven-plugin</artifactId>
          <version>0.7.6.201602180812</version>
          <executions>
            <execution>
              <id>prepare-agent</id>
              <goals>
                <goal>prepare-agent</goal>
              </goals>
            </execution>
          </executions>
        </plugin>

        <plugin>
          <groupId>org.eluder.coveralls</groupId>
          <artifactId>coveralls-maven-plugin</artifactId>
          <version>4.3.0</version>
        </plugin>

      </plugins>
    </pluginManagement>
  </build>
</project>

持續整合

之前嘗試在阿里雲上搭Jenkins ,因為記憶體爆炸(免費機) ,以失敗告終.在新增SCM節點時 ,搜尋了一下整合的工具 ,發現了 Travis.Travis是一個持續整合的平臺 ,自帶與GitHub的整合 ,能夠檢測程式碼提交併觸發繼承指令碼.

• 進入官網使用GitHub登入 ,然後選擇想要繼承的repo
• 在repo下新建.travis.yml檔案 ,寫入自動整合觸發的指令碼
• push程式碼到github ,然後就可以到travis首頁檢視編譯情況

coveralls是一個測試報告展示平臺 ,能夠整合多種測試報告 .也是在使用travis的時候檢索到的 ,通過travis持續整合並生成測試報告 ,然後上傳到coveralls .

• 使用GitHub賬號登入 ,選擇repo
• 複製repoToken
  

repoToken是你訪問測試報告的憑證 ,因此不能明文上傳到github上 ,但是我們又需要在CI中使用這個repoToken.

加密Token

• 使用travis的對稱加密工具(需要ruby gem工具):travis encrypt COVERALLS_TOKEN=xxxxxx
• 複製加密後的token到.travis.yml檔案中
• 使用變數名訪問

在travis指令碼中使用token和測試報告生成工具

生成並上傳測試報告

Java專案官方推薦了一個plugin使用 ,token不能使用明文 ,所以不能直接把token配置在pom中.而是在travis整合時 ,把解密後的token拿來使用.

<build>
    <plugins>
    <!-- 直接引用parent中配置好的plugin -->
      <plugin>
        <groupId>org.jacoco</groupId>
        <artifactId>jacoco-maven-plugin</artifactId>
      </plugin>
      <plugin>
        <groupId>org.eluder.coveralls</groupId>
        <artifactId>coveralls-maven-plugin</artifactId>
      </plugin>
    </plugins>
  </build>

language: java
sudo: false
script: mvn clean verify
after_success:
  - mvn clean test
  ## 生成測試報告
  - mvn jacoco:report
  ## 獲取travis解密的token ,並呼叫coveralls-plugin上傳報告
  - mvn coveralls:report -DrepoToken="${COVERALLS_TOKEN}"

## 加密後的token字串
env:
  global:
    - secure: "..............................."

最後

就可以在主頁上看到持續整合和測試報告的結果 ,還可以匯入非常有逼格的budge