.travis.yml: force xenial for docker builds #46
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
Apparently, even though Travis-CI is moving to use Xenial (16.04) dockers, some Trusty dockers are still lurking around and randomly being assigned to builds. For this repo in particular, Trusty seems to be allocated mostly. Force Xenial, since that will be the next default docker image in a few months. This fails because of `EXTRA_SSH=-oHostKeyAlgorithms=+ssh-dss` where the build complains that: ``` sftp -oHostKeyAlgorithms=+ssh-dss [secure]@[secure] command-line line 0: Bad protocol 2 host key algorithms '+ssh-dss'. ``` We could remove the EXTRA_SSH stuff in the build, but we'd get the error that the EXTRA_SSH option is fixing. So, just default to Xenial docker images (for docker builds), add a note about it in the `.travis.yml` and change later. We will need to re-update builds at some point in time anyway. Signed-off-by: Alexandru Ardelean <[email protected]>
adisuciu
approved these changes
Jul 25, 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.
Apparently, even though Travis-CI is moving to use Xenial (16.04) dockers,
some Trusty dockers are still lurking around and randomly being assigned to
builds.
For this repo in particular, Trusty seems to be allocated mostly.
Force Xenial, since that will be the next default docker image in a few
months. This fails because of
EXTRA_SSH=-oHostKeyAlgorithms=+ssh-dsswhere the build complains that:
We could remove the EXTRA_SSH stuff in the build, but we'd get the error
that the EXTRA_SSH option is fixing.
So, just default to Xenial docker images (for docker builds), add a note
about it in the
.travis.ymland change later. We will need to re-updatebuilds at some point in time anyway.
Signed-off-by: Alexandru Ardelean [email protected]