Hi All,
For a while now I've been using the patchwork[3] event mechanism to push
test branches to github->travis: you can see the various series branches
here https://travis-ci.org/toastertester/toaster-next/branches
If you want to test your Toaster patches using Travis rather than
locally or by sending them to the mailing list you can:
1) Login to Github
2) Click on "Fork" the repository button on
https://github.com/toastertester/toaster-next
3) Clone or add your new fork as a remote e.g. git remote add
my-toaster-next [email protected]:username/toaster-next.git or git clone
[email protected]:username/toaster-next.git
4) Do your work, add some commits
5) Do a git push to my-toaster-next or in your forked repo
6) Go back to the web page for your forked repository and hopefully if
you haven't got any conflicts you can then click "New pull request"
An example of this is https://github.com/toastertester/toaster-next/pull/1
Which creates a test run on Travis automatically see:
https://travis-ci.org/toastertester/toaster-next/pull_requests
OR
Instead of all of the above you could set up your own Travis and
Github[1] and add the .travis.yml[2] in the root of your repository as
an additional patch you carry
Michael
[1] https://travis-ci.org/
[2]
https://github.com/toastertester/toaster-next/blob/toaster-next/.travis.yml
[3] https://patchwork.openembedded.org/project/toaster/
--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster
