In this example:

• Using Cloud Native Build to package Spring Boot + Gradle project, build Docker image and publish to artifact repository
• Configured build.gradle and gradle-wrapper.properties to use Tencent Cloud's Maven Mirror and Gradle Wrapper Mirror for acceleration

1. Use Cloud Native Build (CNB) to build your project
2. Write a Dockerfile
3. Declarative build cache
4. Understand environment variables and their usage
5. Learn how to use Docker artifact repository
6. Configure .ide/Dockerfile for Cloud Native Development

1. Command line execution

# Run in terminal
$ ./gradlew bootRun

2. Debug Mode

• Click the "Run and Debug" icon in the activity bar on the left side of VS Code, select "Launch file" from the run and debug drop-down list, and then click the green run button (or press F5 directly). View configuration

The project integrates JUnit 5 and Mockito testing frameworks, and uses Jacoco for code coverage analysis.

Run all tests:

# Run all unit tests
$ ./gradlew test

View test report:

# Test report location
$ open build/reports/tests/test/index.html

The project uses Jacoco plugin to generate code coverage reports:

# Generate code coverage report
$ ./gradlew jacocoTestReport

# View coverage report
$ open build/reports/jacoco/index.html

Run comprehensive quality checks (including tests, coverage and code style):

# Run all code quality checks
$ ./gradlew codeQualityCheck

The project integrates Checkstyle to ensure code quality and consistency. Checkstyle is a development tool that helps Java programmers adhere to coding standards.

You can run Checkstyle check with the following command:

# Run Checkstyle check
$ ./gradlew checkstyleMain

# Generate Checkstyle HTML report
$ ./gradlew checkstyleReport

The generated HTML report is located at build/reports/checkstyle/main.html.

The Checkstyle configuration file is located at config/checkstyle/checkstyle.xml, which uses Google Java style guide by default. You can modify this file to customize the check rules according to project requirements.

Main check rules include:

• Code format and indentation
• Naming conventions for variables, methods and classes
• Whitespace and newline rules
• Comments and Javadoc requirements
• Import statement specifications
• Code structure and design

• Common issue: When Gradle builds Java projects, it downloads Gradle Wrapper according to distributionUrl=https\://services.gradle.org/distributions/gradle-7.6-bin.zip in gradle/wrapper/gradle-wrapper.properties under project root directory, which can be slow.
• Acceleration solution: Change distributionUrl in gradle/wrapper/gradle-wrapper.properties to distributionUrl=https\://mirrors.cloud.tencent.com/gradle/gradle-7.6-bin.zip Reference: Gradle download address.

repositories {
    mavenLocal()
    maven {
        url "https://mirrors.cloud.tencent.com/nexus/repository/maven-public/"
    }
    mavenCentral()
}

allprojects {
    repositories {
        mavenLocal()
        maven {
            url "https://mirrors.cloud.tencent.com/nexus/repository/maven-public/"
        }
        mavenCentral()
    }
}

• When your Java project is relatively large, you can configure the JVM memory size used by Gradle to make the build more efficient. Please refer to https://docs.gradle.org/current/userguide/build_environment.html#sec:configuring_jvm_memory
  • Adjust org.gradle.jvmargs in gradle.properties to set Xmx and Xms to appropriate values.