1. 30 Apr, 2017 1 commit
    • Luca Boccassi's avatar
      Problem: no way to deploy releases to OBS · f126da8b
      Luca Boccassi authored
      Solution: add new tokens to .travis.yml and change ci_deploy.sh
      script to use Github APIs to create a temporary branch at the tag,
      and the OBS APIs to trigger a source service run in the stable and
      draft release projects:
      network:messaging:zeromq:release-stable
      network:messaging:zeromq:release-draft
      
      The branch hack is unfortunately necessary as it is not possible to
      modify OBS sources with the token APIs, and it is also not possible
      to automatically fetch the latest tag in the service files.
      The temporary branch is immediately deleted.
      f126da8b
  2. 09 May, 2016 1 commit
    • Kevin Sapper's avatar
      Problem: Deploying release artifacts is a manual process · b2255811
      Kevin Sapper authored
      Solution: Use travis to deploy these artifacts automatically.
      
      The deployment is triggered by tagging on the zeromq/libzmq repository.
      Of the many builds travis is checking only the default one with
      libsodium and drafts disabled is used for deployment.
      
      For now the results of `make distcheck` are deployed as well as their
      md5 and sha1 hash sums. Further changes may upload a generated
      Changelog as well.
      b2255811