我的团队正在使用keybase.io而不是松弛,我希望我们的Jenkins结果会发布到我们的keybase团队的builds目录中。到目前为止,我有一个后期步骤(我使用声明性管道),如下所示:
post {
success {
sh "echo 'Successful build of my app' | keybase chat send mycoolteam --channel builds"
}
}
我还为我们的'bot'创建了一个密钥库帐户。并在构建框上的jenkins用户下安装并登录。我可以使用类似的
成功地从框中向我们的keybase团队发送消息我看到的错误是这样的:
keybase status
2018-05-05T07:53:41.578999Z ▶ [INFO keybase fork_server_nix.go:34] 001 Starting keybase.service.
Job for keybase.service failed because the control process exited with error code. See "systemctl --user status keybase.service" and "journalctl -xe" for details.
2018-05-05T07:53:41.713575Z ▶ [ERRO keybase fork_server_nix.go:41] 002 Failed to start keybase.service.
2018-05-05T07:53:41.713609Z ▶ [ERRO keybase fork_server.go:54] 003 Error in spawning server process: exit status 1
2018-05-05T07:53:41.713695Z ▶ [ERRO keybase main.go:90] 004 exit status 1
不幸的是,systemctl和journalctl命令并没有给我任何帮助。如何确保jenkins可以通过管道脚本联系keybase?
更新
在阅读建议here.后尝试使用带键基的-F标志现在错误看起来像
[ERRO keybase main.go:90] 001 dial unix /run/user/112/keybase/keybased.sock: connect: no such file or directory