Answers: <p>Instead of using Travis' deployment features, build the deployment logic in to your normal "test" script(s). For a PaaS this might be as simple as pushing to another git remote if all tests pass, but the sky is the limit.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-02-28T19:57:00.873Z
Answers: 2017-02-28T19:57:00.873Z
Answers: coderanger
Answers: <p>Travis CI supports <a href="https://docs.travis-ci.com/user/deployment" rel="nofollow noreferrer">deployment</a> on branch release by using the following syntax:</p>
  
  <pre><code>deploy:
    on:
      branch: release
  </code></pre>
  
  <p>The problem is that GitHub does not support it.</p>
  
  <p>As per <a href="https://docs.travis-ci.com/user/deployment/releases/" rel="nofollow noreferrer">GitHub Releases Uploading</a> page at Travis CI:</p>
  
  <blockquote>
    <p>Please note that deploying GitHub Releases works only for tags, not for branches.</p>
  </blockquote>
  
  <p>For GitHub the only workaround is to push tags (e.g. <code>git push origin master --tags</code>).</p>
  
  <p>Or solution is to use different <a href="https://docs.travis-ci.com/user/deployment" rel="nofollow noreferrer">supported provider</a>.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-03-18T13:34:03.803Z
Answers: 2017-03-18T13:34:03.803Z
Answers: kenorb
Body: <p>I'd like to deploy files using Travis CI and it only works for a tagged commit. When committing to the branch, there is a warning:</p>
  
  <blockquote>
    <p>Skipping a deployment with the releases provider because this is not a tagged commit.</p>
  </blockquote>
  
  <p>Is there any way to deploy on branched commit using Travis CI?</p>
  
  <p>To clarify, it works when I tag the commit, but I'd like to deploy files on each commit for the given branch.</p>
  
Comments: CC BY-SA 3.0
Comments: 2017-02-28T18:20:01.727Z
Comments: Have you tried tagging the commit?
Comments: Dave Swersky
Comments: CC BY-SA 3.0
Comments: 2017-02-28T18:20:38.217Z
Comments: It works for the tags, but I'd like to deploy files on every commit.
Comments: kenorb
Tags: <git><release><deployment><travis-ci><github>
Title: Is it possible to autodeploy on every commit in a specific branch using Travis CI and GitHub?
UserDisplayName: kenorb
ThreadText: # Is it possible to autodeploy on every commit in a specific branch using Travis CI and GitHub?
  
  (Asked by: username_0 on 2017-02-28)
  
  I'd like to deploy files using Travis CI and it only works for a tagged commit. When committing to the branch, there is a warning:
  
  > Skipping a deployment with the releases provider because this is not a tagged commit.
  
  Is there any way to deploy on branched commit using Travis CI?
  
  To clarify, it works when I tag the commit, but I'd like to deploy files on each commit for the given branch.
  
  **Tags:** git, release, deployment, travis-ci, github
  
  > **Comments:**
  > **username_1**: Have you tried tagging the commit?  
  > **username_0**: It works for the tags, but I'd like to deploy files on every commit.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2017-03-18. Score: 4 | Accepted answer
  
  Travis CI supports [deployment](https://docs.travis-ci.com/user/deployment) on branch release by using the following syntax:
  
  ```
  deploy:
    on:
      branch: release
  
  ```
  
  The problem is that GitHub does not support it.
  
  As per [GitHub Releases Uploading](https://docs.travis-ci.com/user/deployment/releases/) page at Travis CI:
  
  > Please note that deploying GitHub Releases works only for tags, not for branches.
  
  For GitHub the only workaround is to push tags (e.g. `git push origin master --tags`).
  
  Or solution is to use different [supported provider](https://docs.travis-ci.com/user/deployment).
  
  
  ---
  
  ### Answer by username_2 on 2017-02-28. Score: 6
  
  Instead of using Travis' deployment features, build the deployment logic in to your normal "test" script(s). For a PaaS this might be as simple as pushing to another git remote if all tests pass, but the sky is the limit.
  
  
  ---
  
  