PostgreSQL is a fast-moving database beast. We’re big
fans and very happy users of it ourselves, with
Travis CI running on a total of eight database servers.
For the longest time, all we had to offer to our users and customers was the
standard 9.1 distribution that comes with Ubuntu 12.04. But since then,
PostgreSQL has moved on, bringing more and more feature goodies with every
release.
Release 9.2
brought the new JSON data type and support to fetch data directly from indexes
(very relevant to us too), and
9.3 brought
materialized views, even more goodness for JSON data types and greatly improved
shared memory requirements along the way.
Being able to test against newer versions of PostgreSQL then, was long overdue!
Today we’re happy to ship support for three different versions, 9.1, 9.2 and
9.3, all pulled directly from PostgreSQL’s APT
repository. All come with
PostGIS 2.1 preinstalled and enabled!
How can you start testing against different PostgreSQL versions on Travis CI?
We added a new addon for this. To test your project against 9.3, add this to
your .travis.yml
addons:
postgresql: 9.3
You can pick one of 9.1, 9.2 or 9.3 as a version number. The right version will
already be up and running when your test run starts!
A big thank you to Gilles Cornu for the hard
work he’s put into this feature!
For a while, Travis CI has supported allowed failures in your build matrix -
jobs that are allowed to fail, without affecting the status of the entire build.
However, even if some of the items in your build matrix are allowed failures, Travis CI will still wait for them to finish before marking the build as finished.
Even if all of the other jobs are done, Travis CI won’t mark the build as finished until the allowed failures are done, despite the fact that allowed failures won’t ultimately affect the status of the build.
Today, we’re happy to announce opt-in support for fast finishing on Travis CI. With fast finishing enabled, Travis CI will mark your build as finished as soon as one of two conditions are met:
The only remaining jobs are allowed to fail, or a job has already failed. In these cases, the status of the build can already be determined, so there’s no need to wait around until the other jobs finish.
To enable fast finishing, add fast_finish: true to the matrix section of your .travis.yml, so it looks like this:
Java 8 is close to general availability and being
officially shipped as a stable release. It’s coming packed with lots of
goodies,
including Lambdas!
I don’t know about you, but I’m rather excited about what’s in stock for it.
Heck, almost the entire Travis CI stack runs on the JVM by way of
JRuby.
Today we’re thrilled to announce that Oracle JDK 8 Early Access is now available
for testing on Travis CI!
The fine folks at Oracle (and us, of course!) would love for you to try it out
and make sure all bugs and issues are ironed out before the general release.
To start building your projects on JDK 8, update your .travis.yml to include
oraclejdk8:
language: java
jdk:
- oraclejdk8
This is a great opportunity to not only make sure your code runs properly on the
upcoming release, but also to report any bugs that come up trying it out. The
folks from Oracle would love to hear your
feedback, be it bugs, issues, or success
stories. For deeper discussion, make sure to follow the JDK
8 mailing list
JRuby is already testing on JDK 8, now it’s your turn!
