Finatra 1.5.3 and dependencies at Travis CI

[pvoznenko]

Hi guys,

Could you maybe help me, recently my builds in Travis CI start failing since some dependencies disappeared from Twitter repos (or been moved). Strange thing is that it is totally fine working locally.

Maybe some resolvers\dependencies are missing in my build.sbt?

Error in Travis CI:

[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: org.apache.thrift#libthrift;0.5.0: not found
[warn]  :: com.twitter.common#metrics;0.0.9: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::

Link to build log in Travis CI: https://travis-ci.org/pvoznenko/finatra-angular-example/builds/61740360

My build.sbt:

scalaVersion := "2.10.4"

libraryDependencies ++= Seq(
  "com.twitter" %% "finatra" % "1.5.3",
  "com.typesafe.slick" %% "slick" % "2.1.0",
  "org.slf4j" % "slf4j-nop" % "1.6.4",
  "com.h2database" % "h2" % "1.4.182"
)

resolvers ++= Seq(
    "Twitter Maven" at "http://maven.twttr.com",
    "Finatra Repo" at "http://twitter.github.com/finatra"
)

Link to build.sbt file: https://github.com/pvoznenko/finatra-angular-example/blob/master/build.sbt

Google not helpful :(

Would be really happy to get advice where to dig or what is wrong.

Best regards,
Pavlo Voznenko

[travisbrown]

This is a problem with the maven.twttr.com repository—some changes were recently made to the server that are causing intermittent failures.

There are a few workarounds, but running SBT with -Dhttp.keepAlive=false seems to be the most effective. In your Travis CI config, for example, you can use something like this:

before_script: sbt -Dhttp.keepAlive=false update

This will cause the dependency resolution and downloading steps to be run first separately with this setting. You could also use travis_retry in this command, or turn on Travis CI's artifact caching, but just setting the property should work.

We're hoping to get this issue fixed soon (possibly as soon as next week), and in the longer term we're planning to eliminate the need for this repository altogether (see my comment here for some more context). In the meantime apologies for the inconvenience.

[pvoznenko]

Thank you @travisbrown , it helped.