goplus / community

Go+ Community written in Go+
Apache License 2.0
11 stars 15 forks source link

deploye: add release build config #267

Closed LiusCraft closed 7 months ago

qiniu-prow[bot] commented 7 months ago

@LiusCraft: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
community-pull-preview-environment-test 98253c69791c658360b4f72433db7e4e49e6d7ed link true /test community-pull-preview-environment-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
qiniu-prow[bot] commented 7 months ago

@LiusCraft: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
community-pull-preview-environment-test a58802793d5b168484a04dd84cbcaf4363142a1b link true /test community-pull-preview-environment-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
qiniu-ci commented 7 months ago

The PR environment is ready, please check the PR environment

[Attention]: This environment will be automatically cleaned up after 6 hours, please make sure to test it in time. If you have any questions, please contact the author of the PR or the community team.