Add windows CI entry point script to repo#35362
Conversation
Signed-off-by: Daniel Nephin <[email protected]>
fcdca47 to
f671ada
Compare
Signed-off-by: Daniel Nephin <[email protected]>
|
SGTM |
|
ping |
|
ping @jhowardmsft PTAL |
|
Can this be named |
|
Asked @seemethere on Slack to have a look |
|
@thaJeztah The only thing we really need for this to work for Docker CE/EE specific testing is a way to pass a CLI binary in, for everything else I can write a wrapper script for our internal CI. |
The script filename should match the jenkins build. If there are parts of this that can be shared then maybe it can be refactored. |
|
It's identical for all RS builds so far (1..5). Hence it should just be "RS" without the moniker |
|
Looks like this PR should be closed because PR #37715 already brought in |
This change is a requirement for #34226.
This change also brings the windowsRS1 build in line with all the other builds, which have an entry point at
hack/ci. The windowsRS1 config has been updated to call this script.This change is important because currently the configuration in jenkins makes too many assumptions about the repo and artifacts created by the build. We need a minimal interface between our CI configuration and the repo, so that we are free to make changes in a PR without requiring complicated acrobatics to support those changes in CI.
cc @johnstep @jhowardmsft @tiborvass