lark-notice-plugin is a build notification robot notification plug-in for Jenkins, which can push the Jenkins build process and result notifications to Lark, Feishu, DingTalk, and WeCom collaboration platforms. Multiple notification timings can be configured, including build start, build interruption, build failure, build success, build instability, etc. Supports many different types of messages, including text messages, image messages, link messages, markdown messages, rich text messages, and card messages. The plug-in also provides the functions of custom template and variables, allowing you to customize the content and format of notification messages according to your own needs.

Please refer to official document

• Fast test suite: mvn test
• Full suite including JenkinsRule page and integration tests: mvn test failsafe:integration-test failsafe:verify -Pjenkins-rule-tests

Add hpi:run to the startup configuration in the maven control panel on the right side of IDEA:

1. set MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=5005,suspend=n
2. mvn hpi:run -Djetty.port=8080

1. Open the maven panel in idea, the hpi plugin under Plugins
2. Right click on hpi:run and select Modify Run Configuration.. to set
3. Click Modify Options and select Add VM Options option
4. Input at VM options: -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=5005,suspend=n
5. Click the Run button to start executing the maven command (do not run in Debug mode)

1. Open Run/Debug Configurations and click Add New Configuration and select Remote JVM DEBUG
2. After configuring the port, Run runs the debugger
3. The console prints information after startup: Listening for transport dt_socket at address: 5005

1. Use Alibaba Java Coding Guidelines Verify code specifications.
2. Use the Google Style Guide to unify the code style.

IDEA

download intellij-java-google-style.xml

Import via Settings -> Editor Code Style.

• Plugin tutorial
• Jenkins plug-in development journey: from idea to release in two days (Part 1)
• Jenkins plug-in development journey: from idea to release in two days (Part 2)