Skip Menu |

This queue is for tickets about the Dist-Zilla-Plugin-GitHub CPAN distribution.

Report information
The Basics
Id: 101976
Status: open
Priority: 0/
Queue: Dist-Zilla-Plugin-GitHub
People
Owner: Nobody in particular
Requestors: ether [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Fri Feb 06 13:08:06 2015 ether [...] cpan.org - Ticket created
Subject: wishlist: option to enable travis for the repository
It would be really cool if: [GitHub::Create] travis = 1 ..would make the API hit to enable travis testing for the repo. It's probably pretty straightforward.. just need to find the right API to hit.
  Sat Feb 07 06:58:34 2015 ALEXBIO [...] cpan.org - Correspondence added
On Fri Feb 06 13:08:06 2015, ETHER wrote: Show quoted text
> It would be really cool if: > > [GitHub::Create] > travis = 1 > > ..would make the API hit to enable travis testing for the repo. > > It's probably pretty straightforward.. just need to find the right API > to hit.
Note that travis has its own API. I've never done this, but I think that you need to first create a GitHub auth token [0], then authenticate on travis [1], synchronize the user [2] and finally enable the hook [3]. Don't know if you can do the whole thing using the GitHub API alone. Cheers [0] http://docs.travis-ci.com/api/#creating-a-temporary-github-token [1] http://docs.travis-ci.com/api/#with-a-github-token [2] http://docs.travis-ci.com/api/#users [3] http://docs.travis-ci.com/api/#hooks
  Sat Feb 07 06:58:35 2015 The RT System itself - Status changed from 'new' to 'open'
  Sat Feb 07 13:46:04 2015 ether [...] cpan.org - Correspondence added
On 2015-02-07 03:58:34, ALEXBIO wrote: Show quoted text
> Note that travis has its own API. I've never done this, but I think > that you > need to first create a GitHub auth token [0], then authenticate on > travis [1], > synchronize the user [2] and finally enable the hook [3]. Don't know > if you can > do the whole thing using the GitHub API alone. > > Cheers > > [0] http://docs.travis-ci.com/api/#creating-a-temporary-github-token > [1] http://docs.travis-ci.com/api/#with-a-github-token > [2] http://docs.travis-ci.com/api/#users > [3] http://docs.travis-ci.com/api/#hooks
I was assuming that we could ignore the first few steps, as they only need to be done once per user -- after that, isn't it just a matter of adding the web hook on the repository? that's in https://github.com/<user>/<repository>/settings/hooks in the web gui.
  Sun Feb 08 09:08:10 2015 ALEXBIO [...] cpan.org - Correspondence added
On Sat Feb 07 13:46:04 2015, ETHER wrote: Show quoted text
> On 2015-02-07 03:58:34, ALEXBIO wrote: >
> > Note that travis has its own API. I've never done this, but I think > > that you > > need to first create a GitHub auth token [0], then authenticate on > > travis [1], > > synchronize the user [2] and finally enable the hook [3]. Don't know > > if you can > > do the whole thing using the GitHub API alone. > > > > Cheers > > > > [0] http://docs.travis-ci.com/api/#creating-a-temporary-github-token > > [1] http://docs.travis-ci.com/api/#with-a-github-token > > [2] http://docs.travis-ci.com/api/#users > > [3] http://docs.travis-ci.com/api/#hooks
> > I was assuming that we could ignore the first few steps, as they only > need to be done once per user -- after that, isn't it just a matter of > adding the web hook on the repository? that's in > https://github.com/<user>/<repository>/settings/hooks in the web gui.
I think you'd still need to somehow notify travis that you added a new repository. Again, I've never done this, so I could be wrong.