# My rust releases builds are not pushed to GitHub releases

**URL:** <https://travis-ci.community/t/my-rust-releases-builds-are-not-pushed-to-github-releases/4278>\
**Category:** Rust\
**Created:** [July 19, 2019, 2:20pm UTC](https://travis-ci.community/t/my-rust-releases-builds-are-not-pushed-to-github-releases/4278 "2019-07-19T14:20:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Riduidel](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/riduidel/32/2280_2.png) [@Riduidel](https://travis-ci.community/u/Riduidel)\
**Post date:** [July 19, 2019, 2:20pm UTC](https://travis-ci.community/t/my-rust-releases-builds-are-not-pushed-to-github-releases/4278/1 "2019-07-19T14:20:54Z")

</div>

On [https://travis-ci.org/Riduidel/rrss2imap](https://travis-ci.org/Riduidel/rrss2imap) I’m trying to have Travis generate mult-platform releases.  
My .travis.yml file is there [https://github.com/Riduidel/rrss2imap/blob/master/.travis.yml](https://github.com/Riduidel/rrss2imap/blob/master/.travis.yml)

To perform a release, as of today, I run `cargo release`.

When doing so, a tag is put on my repository, the release is pushed to [crates.io](http://crates.io), and a build is triggered on travis.  
I expect that build to push release artifacts to GitHub (thanks to the [deploy job](https://github.com/Riduidel/rrss2imap/blob/master/.travis.yml#L52)).  
Unfortunatly, even if the deploy task is indicated as finishing correctly, nto the slightest artifact is pushed on GitHub releases.

What am i doing wrong ? And how can I fix that ?

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [July 19, 2019, 9:14pm UTC](https://travis-ci.community/t/my-rust-releases-builds-are-not-pushed-to-github-releases/4278/2 "2019-07-19T21:14:36Z")

</div>

Specifying `verbose: true` under `deploy:` should give more information on what is happening.

In particular, `draft: true` looks suspicious. [Docs say](https://docs.travis-ci.com/user/deployment/releases/#draft-releases-with-draft-true) that draft releases are only visible to collaborators.

`${GITHUB_OAUTH}` is another suspect. `.travis.yml` is parsed by a specific library, not by Bash, that might not support this syntax of variable substitution.
