Cron job in travis may disrupt the release process
In case of bad timing, cron job can publish bindings earlier than the release job and in this case the release job will fail.
E.g. pulp_rpm job which publishes bindings to pypi failed saying that such version already exists https://travis-ci.org/pulp/pulp_rpm/builds/598783999.
An hour earlier a cron job published those bindings.
There were multiple issues during release process, so the version of new release stayed unchanged in the master for few hours. That's why cron job released the version of a beta release and not the .dev (nightly) one which is usually set on the master branch.
Maybe it's one more reason to do branching for our releases or some other adjustment for a release process to avoid this problem.
Please register to edit this issue