ci: update one-pipeline to 1.3.0 - #12188
Conversation
|
Hi! 👋 Thanks for your pull request! 🎉 To help us review it, please make sure to:
If you need help, please check our contributing guidelines. |
This comment has been minimized.
This comment has been minimized.
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
There was a problem hiding this comment.
More details
The 1.3.0 tag preserves the published pipeline-template contract from 1.2.0. Its only upstream behavioral change adds a statically linked probe server, which handled repeated probes and failed cleanly for invalid or occupied ports.
📊 Validated against 10 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit d26fd51 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
|
/merge -f --reason "One pipeline update, already tested as pert of PR GitLab pipeline" |
|
View all feedbacks in Devflow UI.
The expected merge time in
Warning This change was merged without running any pre merge CI checks Reason: One pipeline update, already tested as pert of PR GitLab pipeline |
cf43b46
into
master
This automated pull request updates one-pipeline to
1.3.0.📝 Full release notes