[wip] Break e2e tracking into its own service

[eparis]

The e2e stuff has a life of its own and is too tightly coupled with the merge queue. This starts the coding to break all of the e2e stuff into its own service (which the merge queue can make use of)

---

This change is

[eparis]

@lavalamp

[lavalamp]

really? :)

[lavalamp]

I'll look more later-- only comment so far is don't check the e2e-tests binary in :)

[lavalamp]

So I don't know if I understand the intention here-- do you want the submit queue to be looking at this second service? Or will they both be checking the tests?

(I want to make this start checking presubmit runs to file issues. I'll try to not make your rebase too hard. Alternatively if you want to split off something that does the rename & moves I could rebase on top of that?)

[eparis]

I intend to move all of the e2e stuff to its own daemon which the submit queue will talk to.

Everything that runs against all open PRs in one daemon. Everything that deals with the e2e tests in its own daemon. Completely decoupling the logic. More micro-servicy :)

I'd say just keep doing what you want to do. Because I don't know when I'll have time to finish that separation...

[lavalamp]

Sounds good. Thanks!

On Mon, Jun 27, 2016 at 11:46 AM, Eric Paris notifications@github.com
wrote:

I intend to move all of the e2e stuff to its own daemon which the submit
queue will talk to.

Everything that runs against all open PRs in one daemon. Everything that
deals with the e2e tests in its own daemon. Completely decoupling the
logic. More micro-servicy :)

I'd say just keep doing what you want to do. Because I don't know when
I'll have time to finish that separation...

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1210 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAnglpbhAbftnpKc5-lUA4a97WjU2_p-ks5qQBqegaJpZM4I136W
.

[k8s-github-robot]

@eparis PR needs rebase

[test-foxish]

recomputing cla status...

[k8s-github-robot]

[CLA-PING] @eparis

Thanks for your pull request. It looks like this may be your first contribution to a CNCF open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://identity.linuxfoundation.org/projects/cncf to sign.

Once you've signed, please reply here (e.g. "I signed it!") and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.

[eparis]

@foxish who owns setting the cla/linuxfoundation ? It's getting me wrong (and who knows how many other Red Hatters) so I want to know who to talk with...

[foxish]

@eparis, could you explain on kubernetes/kubernetes#27796? @caniszczyk should be able to help out.

[emsearcy]

Bump (signed it?). (edit: worked, cla/linuxfoundation no->yes)