[GitHub] [incubator-dubbo] satansk opened issue #3393: [Discuss] Provide command to rerun the CI

["satansk (GitHub)" <gi...@apache.org>]

For now, the CI seems unstable and sometimes it failed, and it will succeed after a rebuild. I have encoutered this problem several times, and so as some other contributor(https://github.com/apache/incubator-dubbo/pull/3389).

Do we have or should we have any command to start a rebuild?

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3393 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] ralf0131 commented on issue #3393: [Discuss] Provide command to rerun the CI

["ralf0131 (GitHub)" <gi...@apache.org>]

I wish it could. 

In fact, dubbo-bot does not have the permission to trigger the build, either. :(
To trigger the build, a write access to the repo is needed.

If you want to trigger it manually without letting the committers to know, you can commit an empty message.


[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3393 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] satansk commented on issue #3393: [Discuss] Provide command to rerun the CI

["satansk (GitHub)" <gi...@apache.org>]

Sounds reasonable, committers can trigger it manually and contributors can trigger by an empty commit, that's what I want. Thanks @ralf0131 :)

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3393 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] ralf0131 commented on issue #3393: [Discuss] Provide command to rerun the CI

["ralf0131 (GitHub)" <gi...@apache.org>]

> > If you want to trigger it manually without letting the committers to know, you can commit an empty message.
> 
> @ralf0131 Yes that's what I've done in #3389

Before you do that, it is better to save the error log, and report to the community to investigate.

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3393 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] kezhenxu94 commented on issue #3393: [Discuss] Provide command to rerun the CI

["kezhenxu94 (GitHub)" <gi...@apache.org>]

Can @dubbo-bot help in this situation? What I mean is that if dubbo-bot can trigger the rebuild task, we can do something like this:

Mention dubbo-bot in the comment, such as:

> @dubbo-bot test this please

or something like this. Then @dubbo-bot can trigger the build task, this may need more investigation in travis-ci and the GitHub hooks

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3393 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] satansk closed issue #3393: [Discuss] Provide command to rerun the CI

["satansk (GitHub)" <gi...@apache.org>]

[ issue closed by satansk ]

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3393 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] ralf0131 commented on issue #3393: [Discuss] Provide command to rerun the CI

["ralf0131 (GitHub)" <gi...@apache.org>]

Currently only committer has the permission to trigger the re-build. 
I think what we can do for now is:
- identify why is the UT unstable and fix it
- contributors can request any of the committers to trigger it manually or asking on the mail list for help.

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3393 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] kezhenxu94 commented on issue #3393: [Discuss] Provide command to rerun the CI

["kezhenxu94 (GitHub)" <gi...@apache.org>]

> If you want to trigger it manually without letting the committers to know, you can commit an empty message.

@ralf0131 Yes that's what I've done in #3389 

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3393 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org