feat(取证): 开机自报这份 jar 出自哪笔 commit
制品名自始没 bump 过(aiimage-backend-0.0.1-SNAPSHOT.jar),pom 也没有 git-commit-id, 所以出问题时光看线上机器答不出"在跑的是哪版代码"——10-07 那次是靠"哪个类只有那笔才有"人工认的。 不用 git-commit-id 插件:现网出包是 mvn -o 离线,新插件当场解析失败,等于给发布通道加一根 只有联网才通的管子。改成打包前由 scripts/_git_stamp.py 生成 src/main/resources/git.properties (已加进 .gitignore,入库就成孤儿构建产物,target/classes 里那个孤儿 V148 就是这么来的), 开机念 [build-info];念不到时打 [build-info-missing] 而不是静默当干净构建。 拒绝的职责不在这里:一个元数据文件读不到不该把在跑实例打死,那是发布闸门的事。
This commit is contained in:
@@ -0,0 +1,135 @@
|
||||
package com.nanri.aiimage.config;
|
||||
|
||||
import static org.junit.jupiter.api.Assertions.assertEquals;
|
||||
import static org.junit.jupiter.api.Assertions.assertFalse;
|
||||
import static org.junit.jupiter.api.Assertions.assertNotNull;
|
||||
import static org.junit.jupiter.api.Assertions.assertNull;
|
||||
import static org.junit.jupiter.api.Assertions.assertTrue;
|
||||
|
||||
import java.nio.charset.StandardCharsets;
|
||||
import java.util.List;
|
||||
|
||||
import org.junit.jupiter.api.Test;
|
||||
import org.junit.jupiter.api.io.TempDir;
|
||||
import org.springframework.core.io.ByteArrayResource;
|
||||
import org.springframework.core.io.FileSystemResource;
|
||||
import org.springframework.core.io.Resource;
|
||||
|
||||
import ch.qos.logback.classic.Level;
|
||||
import ch.qos.logback.classic.Logger;
|
||||
import ch.qos.logback.classic.spi.ILoggingEvent;
|
||||
import ch.qos.logback.core.read.ListAppender;
|
||||
|
||||
/**
|
||||
* 构建章的读法与"念出来"的级别。
|
||||
*
|
||||
* <p>这些用例要防的形状是:读不到章时静默当作干净构建。所以每条都同时断言
|
||||
* **说了什么**(describe)与**用什么级别说**(WARN/INFO),后者才是巡检能数到的那一部分。
|
||||
*/
|
||||
class BuildInfoLoggerTest {
|
||||
|
||||
private static final String STAMP =
|
||||
"commit=3a49f5f8b1c2d3e4f5061728394a5b6c7d8e9f00\n"
|
||||
+ "branch=master\ndirty=false\nbuild_time=2026-10-08T17:00:00+08:00\n";
|
||||
|
||||
private static ByteArrayResource stamp(String body) {
|
||||
return new ByteArrayResource(body.getBytes(StandardCharsets.UTF_8));
|
||||
}
|
||||
|
||||
/** 挂一个 ListAppender 到本类的 logger 上,取回真实落到的事件(不是自己拼字符串)。 */
|
||||
private static List<ILoggingEvent> capture(Runnable body) {
|
||||
Logger logger = (Logger) org.slf4j.LoggerFactory.getLogger(BuildInfoLogger.class);
|
||||
ListAppender<ILoggingEvent> appender = new ListAppender<>();
|
||||
appender.start();
|
||||
logger.addAppender(appender);
|
||||
try {
|
||||
body.run();
|
||||
} finally {
|
||||
logger.detachAppender(appender);
|
||||
appender.stop();
|
||||
}
|
||||
return appender.list;
|
||||
}
|
||||
|
||||
@Test
|
||||
void 章不存在时read返回null而不是空对象(@TempDir java.nio.file.Path dir) {
|
||||
Resource absent = new FileSystemResource(dir.resolve("nope.properties"));
|
||||
assertFalse(absent.exists(), "前提:这个文件确实不存在");
|
||||
assertNull(BuildInfoLogger.read(absent));
|
||||
}
|
||||
|
||||
@Test
|
||||
void 章存在但commit为空要念成empty而不是unknown() {
|
||||
BuildInfoLogger.BuildInfo info = BuildInfoLogger.read(
|
||||
stamp("commit=\nbranch=master\ndirty=false\nbuild_time=T\n"));
|
||||
assertNotNull(info);
|
||||
assertFalse(info.usable());
|
||||
assertTrue(BuildInfoLogger.describe(info).contains("commit=empty"),
|
||||
BuildInfoLogger.describe(info));
|
||||
}
|
||||
|
||||
@Test
|
||||
void 四键齐时逐个解析出来() {
|
||||
BuildInfoLogger.BuildInfo info = BuildInfoLogger.read(stamp(STAMP));
|
||||
assertNotNull(info);
|
||||
assertEquals("3a49f5f8b1c2d3e4f5061728394a5b6c7d8e9f00", info.commit());
|
||||
assertEquals("master", info.branch());
|
||||
assertEquals("false", info.dirty());
|
||||
String line = BuildInfoLogger.describe(info);
|
||||
assertTrue(line.contains("commit=3a49f5f8b1c2"), line);
|
||||
assertTrue(line.contains("dirty=false"), line);
|
||||
}
|
||||
|
||||
@Test
|
||||
void 没章时是WARN且带missing锚点() {
|
||||
List<ILoggingEvent> events = capture(() -> new BuildInfoLogger().logIt(null));
|
||||
assertEquals(1, events.size(), "必须正好落一条,落 0 条说明断言在对着空气打钩");
|
||||
assertEquals(Level.WARN, events.get(0).getLevel());
|
||||
assertTrue(events.get(0).getFormattedMessage().contains(BuildInfoLogger.MISSING_ANCHOR),
|
||||
events.get(0).getFormattedMessage());
|
||||
}
|
||||
|
||||
@Test
|
||||
void commit为空也是WARN() {
|
||||
BuildInfoLogger.BuildInfo info = BuildInfoLogger.read(stamp("commit=\ndirty=false\n"));
|
||||
List<ILoggingEvent> events = capture(() -> new BuildInfoLogger().logIt(info));
|
||||
assertEquals(1, events.size());
|
||||
assertEquals(Level.WARN, events.get(0).getLevel());
|
||||
}
|
||||
|
||||
/**
|
||||
* 脏包(工作树有未提交内容时打的)不能念成正常上线件。
|
||||
* 这一条是"级别"上的分歧点:若有人把 dirty 判断摘掉,这里会从 WARN 变 INFO 而红。
|
||||
*/
|
||||
@Test
|
||||
void dirty为true必须是WARN而不是INFO() {
|
||||
BuildInfoLogger.BuildInfo dirty = new BuildInfoLogger.BuildInfo(
|
||||
"3a49f5f8b1c2d3e4f5061728394a5b6c7d8e9f00", "master", "true", "T");
|
||||
List<ILoggingEvent> events = capture(() -> new BuildInfoLogger().logIt(dirty));
|
||||
assertEquals(1, events.size());
|
||||
assertEquals(Level.WARN, events.get(0).getLevel(), "脏包念成 INFO 就等于巡检看不见");
|
||||
assertTrue(events.get(0).getFormattedMessage().contains("dirty=true"));
|
||||
}
|
||||
|
||||
@Test
|
||||
void 干净且commit对得上才是INFO() {
|
||||
BuildInfoLogger.BuildInfo clean = BuildInfoLogger.read(stamp(STAMP));
|
||||
List<ILoggingEvent> events = capture(() -> new BuildInfoLogger().logIt(clean));
|
||||
assertEquals(1, events.size());
|
||||
assertEquals(Level.INFO, events.get(0).getLevel());
|
||||
assertTrue(events.get(0).getFormattedMessage().contains(BuildInfoLogger.INFO_ANCHOR));
|
||||
}
|
||||
|
||||
/**
|
||||
* 真走一遍监听器:测试 classpath 上没有 git.properties ⇒ 必须吵出来。
|
||||
* 这条不靠反射钉注解,钉的是"开机真的会念"。
|
||||
*/
|
||||
@Test
|
||||
void 开机自检在没有章的classpath上会打missing() {
|
||||
List<ILoggingEvent> events = capture(() -> new BuildInfoLogger().logOnBoot());
|
||||
assertEquals(1, events.size());
|
||||
assertEquals(Level.WARN, events.get(0).getLevel());
|
||||
assertTrue(events.get(0).getFormattedMessage().contains(BuildInfoLogger.MISSING_ANCHOR),
|
||||
events.get(0).getFormattedMessage());
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user