-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-22231 Removed unused and '*' import #179
HBASE-22231 Removed unused and '*' import #179
Conversation
💔 -1 overall
This message was automatically generated. |
0458f9c
to
4b7ca94
Compare
💔 -1 overall
This message was automatically generated. |
Would like to re-run the build before merging it. @petersomogyi Do you know how to retrigger the build? Didn't find that option in Jenkins. |
Probably the failures are unrelated, but triggered a new build now: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-179/3 |
Thanks @petersomogyi. Finally found it in Jenkins. |
How do you do it @HorizonNet ? |
Seems the HDDS project has a magic word to re-trigger a test. It is '/retest'... |
Thanks @Apache9 |
I also know projects where you can do "Jenkins, test this please". For now I just logged into Jenkins, went to the appropriate job and clicked on "Rebuild". |
The previous build link I posted failed. I added the HBASE ID when triggered the build and the job tried to download patch file from Jira. Retriggered it again without specifying HBASE-22231: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-179/4
On hbase-connectors and hbase-operator-tools precommits we have a 'retest build' magic string for which the jenkins reruns the verification. I don't know if it is possible to enable similar this setup. |
How do you do this? I think we can do the same for the main hbase repo. |
Check the job settings, Build Triggers > Use github hooks for build triggering (Advanced) > Trigger phrase |
Oh, the jenkins job for HBase is more complicated, we use yetus and it is a multibranch pipeline job... The config of the sub jobs is auto generated by the jenkins file... Let me see how to add the option in jenkins file... |
OK, seems the '/retest' on HDDS project is a fake one, they just updated the PR and triggered a new pre commit build... |
💔 -1 overall
This message was automatically generated. |
+1, test failure is unrelated. |
Targeted for branch-2.1.