Allow non-standard build directory. #1855
Open
Conversation
This file contains hidden or 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
Fixed docker.target.directory for non-standard build directories.
|
@jdelker : Thanks, could you please add an entry to doc/changelog.md regarding this change? |
|
|
@jdelker : E2E tests seem to be failing. Could you please take a look? |
Well, I'm lacking insight about what really happens in those integration tests to find the source of that failure. |
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.
Currently, the general
outputDirectoryhas a fixed default oftarget/docker, which breaks projects with a diverting${project.build.directory}.This change simply adjusts the default, so this aligns correctly.