[travis] Update to postgres 9.6

[haubourg]

Hi, it seems we are not alone to face issues since 12 days: https://github.com/travis-ci/travis-ci/issues/6972

adding this to config seems to solve the issue but costs 22 seconds of build time:

  apt:
    packages:
    - postgresql-9.6-postgis-2.3

[m-kuhn]

Thanks @haubourg , trying this now

[haubourg]

Thanks @m-kuhn Merged, we now are back to the authentication issue @sylvainbeo

[m-kuhn]

In case you have special characters ("special" in bash context) in the password, have a look at this instruction:

https://github.com/opengisch/qfieldsync/blob/master/.travis.yml#L34

[haubourg]

You mean adding double quotes around secure encrypted key would do?

[m-kuhn]

escaped single quotes + single quotes is what I needed to do.

But without having your password at hand it's very hard to give any guarantees :stuck_out_tongue_winking_eye:

[haubourg]

Oh, before encrypting password then.. I also saw double quote around the key in your travis example. @sylvainbeo we need you then !

[sylvainbeo]

I'm trying that.

[sylvainbeo]

Mmm, in our case we don't encrypt a password but a token, with no special char...

[sylvainbeo]

travis-encrypt -r qwat/qwat-data-sample GH_TOKEN=[xxxxxxxxxxx]

[m-kuhn]

then it shouldn't be an issue...

the same commands executed locally succeed?

[m-kuhn]

export GH_TOKEN=[xxxxxx]
./scripts/deploy.sh # or whatever it is for you

[sylvainbeo]

We don't need to do the export. COnfig is directly in .travis.yml

[sylvainbeo]

@m-kuhn Do you well understand the travis-encrypt command ? I mean, each time we execute it, it override the last generated public token ?

[m-kuhn]

The "clear-text" token was generated once.

Everytime you encrypt it, it generates an encrypted version for this token. I think these encrypted versions can be used interchangeably.

[sylvainbeo]

Ok, that's what i thought