Closed floydkots closed 6 years ago
Just realized the build scripts are unable to login to docker because the credentials are unavailable to it:
Similarly, we do not provide these values to untrusted builds, triggered by pull requests from another repository.
Quoting https://docs.travis-ci.com/user/environment-variables/#defining-variables-in-repository-settings. Needless to say, the build succeeds in my fork.
So, how can I go about this? Should I create a packaging
branch under rebirthdb
, open a pull request and merge to it so that I finally open the pull request from a 'trusted build'? I'm not even sure if it would work.
As for codacy:
MAINTAINER
field, but the docs say MAINTAINER
is deprecated in favor of LABEL
, so I used LABEL
. wget
and curl
in the same dockerfile. However, rebirthdb
's build system and scripts need both.apt-get
packages to specific versions. Well, I don't know, should we?Closing this PR in favour of #24.
Description
Packaging #17
xenial
andtrusty
versions of Ubuntu. Added docker containers into the mix to allow for greater variety in the test environments and packaging. Travis only provides theprecise
andtrusty
version of ubuntu on it's VMs.Known Issues
ClusteringRaft.FailOver
test case fails nondeterministically. At least that's how it looks to me. I can't as yet tell why that happens.Rebranding #14
rethinkdb ...
torebirthdb ...
Known Issues
rethinkdb
. I lean more on the side of piecemeal modifications, as we observe the effects.Updating the README #8
Sponsors
section, currently featuring AIDAX and DigitalOcean.Known Issues
Overally, I think the above steps are in the right direction, but I would like to hear what you guys think before we go for deeper changes.
Also, I'll totally appreciate every help and advice with the known and unknown issues.
Finally, I've left the long commit history, if it might be of any help in contextualizing the changes. I hope that the changes, if approved, will be squashed before being merged.