fix: use fork to build the images #253
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mdelapenya
approved these changes
Oct 28, 2019
kuisathaverat
added a commit
that referenced
this pull request
Nov 3, 2019
This reverts commit 06aa21a.
kuisathaverat
added a commit
that referenced
this pull request
Nov 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
meanwhile, we have permission to merge elastic/docker-jruby#1 we need to build the images with the proper packages. This PR changes the build to pull the code from my personal fork.
Why is it important?
without this change, the Docker images will have a bug, then the Ruby build will fail.