Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Don't run native API tests on travis

We need ES_CLUSTER_NAME to be exported in order for the native
client to successfully connect.
  • Loading branch information...
commit a8d710b60627ee68eb19abcd3499d1a91ce9a06d 1 parent b7e1775
Michael Klishin authored
Showing with 3 additions and 2 deletions.
  1. +1 −1  .travis.yml
  2. +2 −1  project.clj
2  .travis.yml
View
@@ -4,7 +4,7 @@ services:
- elasticsearch
before_install:
- sudo service elasticsearch status
-script: lein2 all test
+script: lein2 all test :ci
jdk:
- openjdk6
- openjdk7
3  project.clj
View
@@ -28,7 +28,8 @@
:facets :facets
:percolation :percolation
:all (constantly true)
- :default (constantly true)}
+ :default (constantly true)
+ :ci (fn [m] (not (:native m)))}
:mailing-list {:name "clojure-elasticsearch"
:archive "https://groups.google.com/group/clojure-elasticsearch"
:post "clojure-elasticsearch@googlegroups.com"}

2 comments on commit a8d710b

davie moston

I guess this is because the travis CI version of ES is incompatible with the one used in elastisch (for native connections)?
As an alternative couldn't you just spin up a new ES instance for the tests through the API (like in https://github.com/elasticsearch/elasticsearch/blob/master/src/test/java/org/elasticsearch/test/integration/AbstractNodesTests.java)

Michael Klishin

Yes. We will do it, I am just not familiar enough with the node API. Feel free to contribute a pull request ;) If it takes keeping an elasticsearch.yml in test resources, that's perfectly fine.

Please sign in to comment.
Something went wrong with that request. Please try again.