-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-16035. Jenkinsfile for Hadoop #459
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
Conversation
fed8369 to
4cfb2e9
Compare
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
this is slick. What happens if someone comments? |
|
Thanks! It shouldn't do anything if INFRA configured the webhook correctly and Jenkins is functioning properly. In order to make this go live, there are three things that need to happen: a) Hadoop PMC needs to make and own a github account, then provide an OAuth token for that account (I'm using Apache Yetus' for this test.) |
BTW, the creds for this account are stored in the Jenkins credential folder for this job. I can send someone the link and they can put the details in. I don't need to know them. |
|
OK, starting this work. Account will be @hadoop-yetus |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
OK, now the build on the jenkins side is green regardless if junit found test results or not. (since not every patch touches java... case in point.) |
|
🎊 +1 overall
This message was automatically generated. |
8b4a58f to
ffb3727
Compare
ffb3727 to
26d29b5
Compare
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
FYI: I have removed the Apache Yetus credentials from the job that was used for testing. Hadoop community will need to provide their own. |
|
testing a reply by mail to see what happens
…On Sat, Jan 19, 2019 at 8:55 PM Allen Wittenauer ***@***.***> wrote:
FYI: I have removed the Apache Yetus credentials from the job that was
used for testing. Hadoop community will need to provide their own.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#459 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AsXnStHXzLT1o0YLnHN5VXxGXQplCwXnks5vE4ZcgaJpZM4Z103l>
.
|
|
(that's stevel; its mapping my cloudera email to the elephant right now. We need to get it its own email address) |
|
Merged. |
Getting the PR out to unblock sanil. Pending tasks 1. Add documentation 2. Add more tests 3. Currently initialization of the stream happens using createStream on admin. We need to find a way to expose the same functionality to low level users. 4. To populate the initial stream, clients need to get a handle on producer and produce the messages. Alternatively, we can support serialization of source data and pass it as config to the system to initialize. We have a hook in place for this but not implemented it completely. 5. Clean up consumed data on the buffer based on the lowest offsets of the consumers. I will create JIRAs for all the pending tasks and fix them iteratively. xinyuiscool ^^ Author: Bharath Kumarasubramanian <[email protected]> Reviewers: Xinyu Liu <[email protected]> Closes apache#459 from bharathkk/single-node-testing
Testing Apache Yetus master branch doing PRs for Hadoop