How to split image-registry about image-registry HOT 8 CLOSED

Minimum viable impl for 1-3 is to re-add hack/ and test/ dir from Origin

from image-registry.

Minimum viable impl for 1-3 is to re-add hack/ and test/ dir from Origin

That's not viable to test-integration to test-extended. The tests won't work against the levels we want.

You like that unit test script? I can copy that in.

from image-registry.

/cc @miminar @dmage @legionus

from image-registry.

You like that unit test script? I can copy that in.

I mean we can either start with go build and go test and imagebuilder and work our way up in complexity until we get something functional, or just copy and run. I see arguments for both but right now I do not have the bandwidth to start from 0 and iterate. Up to you.

from image-registry.

Now with working travis for build and unit test.

@smarterclayton @derekwaynecarr we're going to need images and I don't know how to make that black magic work.

from image-registry.

@deads2k i will pair you up with someone that just went through the process.

from image-registry.

@deads2k this looks great to me, I expected this to be clone of origin but I see you did the vendored approach.

from image-registry.

@deads2k this looks great to me, I expected this to be clone of origin but I see you did the vendored approach.

Yeah, otherwise its a time bomb for the next guy and I know who would be tapped.

from image-registry.