Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discuss] Provide command to rerun the CI #3393

Closed
kun-song opened this issue Jan 30, 2019 · 6 comments
Closed

[Discuss] Provide command to rerun the CI #3393

kun-song opened this issue Jan 30, 2019 · 6 comments

Comments

@kun-song
Copy link
Contributor

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(#3389).

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

@ralf0131
Copy link
Contributor

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.

@kezhenxu94
Copy link
Member

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

@ralf0131
Copy link
Contributor

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.

@kezhenxu94
Copy link
Member

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

@ralf0131
Copy link
Contributor

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.

@kun-song
Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants