gh-pages Travis CI

[iwle]

Hello all,

I would like to know if we have to fork the main repository under our organisation to the new, external account for Travis CI to recognise it as a repository. This is because although I have allowed admin rights to the collaborator, I cannot see the repository in Travis CI.

This is with regards to the Travis CI and auto-publishing documentation.

Thank you, Ian Wu

[kylase-learning]

@iwle are you trying to setup Travis to produce the documentation like https://kylase-learning.github.io/addressbook-level4/ ?

For Travis, you will need to grant access to your personal account from the organisation account.

[iwle]

Hi @kylase-learning thank you for your response. Yes, I am referring to that. Specifically, https://github.com/nus-cs2103-AY1819S2/addressbook-level4/blob/master/docs/UsingTravis.adoc.

I have granted access to the personal account from the organisation account. However, the main repository fails to show up under Travis CI. Does the personal account need to fork the main repo?

Thanks!

[kylase-learning]

Have you tried re-syncing?

If you fork the main repo to your own account, you can run Travis there as well, however, you will need to configure the organisation's Travis properly as this repo will be used for grading.

You can check if your and your organisation accounts are configured properly to use with Travis in the Settings/Applications in Github.

[iwle]

I have tried re-syncing the personal account and it has admin rights to the main repo. However, this is the screen that I get:

[kylase-learning]

You will need to see your organisation on the left. In this case, you need to review and add your organisation. Then the repositories will show up.