[
https://issues.apache.org/jira/browse/ARROW-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618886#comment-16618886
]
Krisztian Szucs commented on ARROW-3260:
----------------------------------------
I've create a PR for reproducing CI build via docker compose:
https://github.com/apache/arrow/pull/2572
So something like the following is possible:
{code:bash}
docker-compose run python flake8
{code}
We could define the linux CI builds in dockerfiles and just simply run them on
travis. We could even benefit from docker's caching mechanism.
> [CI] Make linting a separate job
> --------------------------------
>
> Key: ARROW-3260
> URL: https://issues.apache.org/jira/browse/ARROW-3260
> Project: Apache Arrow
> Issue Type: Wish
> Components: C++, Continuous Integration, Python
> Reporter: Antoine Pitrou
> Priority: Major
>
> When pushing changes I get routinely frustrated because Travis-CI fails early
> on a linting failure. It would be nice if linting (Python, C++) was a
> separate job so as not to disrupt the development workflow so much.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
