Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Run some REST tests against a cluster running in docker containers #39515
Run some REST tests against a cluster running in docker containers #39515
Changes from 7 commits
36ad7e7
0962587
cf69ae3
0244955
02278b6
012e88a
76f8ead
ef0e33a
ef8bbb8
df7c5fb
48eba36
5f6b3f8
aa95613
d6fa767
d86c25d
39b2597
6794c14
8d50f21
4b785b8
c0cac7b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than define a new task here, we should just configure the existing
processTestResources
task to do this. Its job is already to copy stuff into the resources output directory and can be configured like any otherCopySpec
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I specifically wanted to have a
Sync
task to make sure that there are no tests accidentally left in the resources directory when switching branches etc.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
ProcessResources
task already does this.https://github.com/gradle/gradle/blob/master/subprojects/language-jvm/src/main/java/org/gradle/language/jvm/tasks/ProcessResources.java#L30
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we do these with docker exec instead of modifying the entry point?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather not. The test fixtures are transparent w.r.t the technology used to implement them. In general there's nothing docker specific in the build scripts, and the plugin disables everything that can't run if docker is not available. I would like to keep this and thus avoid using docker exec.
Maybe this is a generic enough use-case to add env vars for creating a super-user when bringing up the container if these are present ?