From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-core V1 2/2] travis: Upload assets to github release
Date: Mon, 30 Jan 2017 10:09:56 -0700 [thread overview]
Message-ID: <20170130170956.GC29502@obsidianresearch.com> (raw)
In-Reply-To: <20170130062316.16268-3-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Mon, Jan 30, 2017 at 08:23:16AM +0200, Leon Romanovsky wrote:
> + # Deploy assets to Github releases
> + # https://docs.travis-ci.com/user/deployment/releases/
> + provider: releases
> + api_key:
> + # This is encrypted OAth token generated by
> + # Travis CLI tool (travis setup releases) limited to specific repo.
> + secure: G9sQd578nctgaety6f27P4p5nyrEgXdvMs1g+K2Hj7GPWxBpQ1Jm7kUlahcwfnYXpYqXen9b2dzyGzaLxjLL5rv6rbtOYp9SVrvybQrnJwkB0HCERKVMwEPsLPOB2lMouBDfk4+iUGdxtcw8Y5UU/xqKcAjkHkM5YpF5HauEX1Jj+Ep/XpX5DEcsVmFwkDgPKJOZv/eUgz1eVtXNFIvmSwJ+QuuUz64JpEpKMY4u7bFu0+2qWqACj19P/Rnufxpr+o5yoCuVNVptoRHMIWJiWZsrd2IhmL3knBoPoxNXSOWqQCK6DCW1KYOOVVAfFoD4YWhWrt6MuB3hh7lgLkS0rsdG9+iMlosl4SOkWZF8ZTkmrmtt6yx+s18tFdNI46QKzaA4wS/1hktweIFizYvmEwUCU8sNK5y9PMfDoGJGwiF1FzWrnLItKMiib0sTGO4Umgc0DKTazVRlIJYooOOOnBGubRudNx3elBTy4C/txSmqR39/6GYlvcyUDJMqB/oQJj2erQ5Gu8VykW5zjko6+3miX3C7GFVQ781BLxAdyNl4WRjZ9ibzjMbK3MC7f0ho1hST6cvBBmy2UnIdvB6zMayHZ/gtXKsDqE386k5FwSuTLT2V7942uFRVJiEwhVmgmBzbZND7PTj4s9GPrL2HLlJOgZooRZdx/ZcT/YNPFbA=
So this is a restricted oauth token for your github account then?
You are comfortable with this?
> +if [[ $TRAVIS_TAG == v* ]] && [ "$TRAVIS_OS_NAME" = "linux" ]; then
> + # Let's create release for vX tags only.
> + git archive --prefix rdma-core/ --output rdma-core-$TRAVIS_TAG.tar.gz HEAD
Should be
--prefix rdma-core-$TRAVIS_TAG/
I think..
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-01-30 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 6:23 [PATCH rdma-core V1 0/2] Create semi-automatic release process Leon Romanovsky
[not found] ` <20170130062316.16268-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-30 6:23 ` [PATCH rdma-core V1 1/2] travis: Simplify travis config Leon Romanovsky
2017-01-30 6:23 ` [PATCH rdma-core V1 2/2] travis: Upload assets to github release Leon Romanovsky
[not found] ` <20170130062316.16268-3-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-30 17:09 ` Jason Gunthorpe [this message]
[not found] ` <20170130170956.GC29502-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-30 20:19 ` Leon Romanovsky
[not found] ` <20170130201953.GM6005-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-01-30 21:16 ` Jason Gunthorpe
[not found] ` <20170130211658.GC27111-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-31 8:57 ` Leon Romanovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170130170956.GC29502@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox