CI builds are deployed on the wrong branch

[y-lohse]

Despite this, it seems that CI builds still land on the build branch. It probably comes from the package.json file.

[y-lohse]

The variablke might need to be exported with env or export so it's available for all commands

[y-lohse]

There's also a real risk that multiple travis jobs override the build branch if they run at the same time, potentially publishing a version of the app under a different version number. At least the tag version of the deployment should have a dedicated branch name.

[Crash--]

We decided to not use a branch to store the build before uploading it to our registry. We want to use downcloud.

See cozy/cozy-passwords#10

[drazik]

Also see cozy/cozy-passwords#11.

And I still have a problem when deploying to the registry with all that: https://travis-ci.org/cozy/cozy-passwords/builds/640547425#L328

I'm looking for a solution. I will keep you informed when I fixed this.