You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2019/01/23 16:56:00 UTC

[jira] [Commented] (TINKERPOP-2140) Test build with Docker automatically

    [ https://issues.apache.org/jira/browse/TINKERPOP-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750215#comment-16750215 ] 

stephen mallette commented on TINKERPOP-2140:
---------------------------------------------

I'm ok with using Travis in this regard, so long as it's "fast". are you seeing this as more of a smoke test for docker itself? like will we run it by just doing a build and skipping all tests (don't know if we have that options with the current build script do we)? 

> Test build with Docker automatically
> ------------------------------------
>
>                 Key: TINKERPOP-2140
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2140
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: build-release
>    Affects Versions: 3.3.5
>            Reporter: Florian Hockmann
>            Assignee: Florian Hockmann
>            Priority: Minor
>
> From time to time, we have problems with our Docker build ({{docker/build.sh}}). Unfortunately, these problems aren't always reproducible for different contributors which means that they aren't noticed when a PR gets tested manually, but only later after a contribution was already merged to a release branch.
> [Here|https://github.com/apache/tinkerpop/pull/1026#issuecomment-456816660] is a recent example.
> We should use Travis to also execute the Docker build automatically. That will hopefully at least find some problems like this before it gets merged.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)