英文:
Gitlab Pipeline email - including the actual error
问题
我知道关于Gitlab的项目设置中的集成部分的流水线邮件，但是否有一种方法可以在“失败的流水线邮件”中丰富“实际错误”？
我觉得打开邮件，找到并点击邮件中的链接，点击失败的流水线步骤，然后才能看到编译或单元测试错误是一种非常低效的方式。
如果该邮件能够简单地包含（甚至以此开始）流水线输出的最后25行，那将会非常有帮助。这样我就可以修复错误，甚至不需要返回Gitlab再尝试另一个构建。在这个工作流程中，我计算了2-3次不必要的点击。
注意：我正在使用Java和Maven，但这个问题适用于所有语言和所有类型的项目。
英文:
I know about Gitlab's Project --> Setting --> integrations -->Pipelines emails, but is there a way to enrich the 'failed pipeline email' with the actual error ?
I find it very inefficient to have to open the email, find and click on the link in the email, click on the failed pipeline step, and only then see what compilation or unit-test error made it into the system.
If that email would simply include (or even start with) the last 25 lines of the pipeline's output that would help a lot. Then I could fix the error and wouldn't even have to go gitlab and back to try another build. I'm counting 2-3 unnecessary clicks in this workflow.
Note: I'm using Java with maven - but this question applies to all languages, all types of projects.
答案1
得分: 1
这在过去是可能的，但被有意地移除了。请参考这个合并请求的原因：https://gitlab.com/gitlab-org/gitlab/-/merge_requests/42395
英文:
This was possible in the past but intentionally removed.
See this merge request why:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/42395
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论