Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

repo with different package folders #117

Closed
jwijffels opened this issue Feb 4, 2019 · 3 comments · Fixed by #152
Closed

repo with different package folders #117

jwijffels opened this issue Feb 4, 2019 · 3 comments · Fixed by #152
Labels

Comments

@jwijffels
Copy link

I'm trying out this package to see if I can publish automatically to a drat repo.
For this github repo which contains currently 7 R package folders https://github.com/bnosac/image
I'm getting the error that there is no DESCRIPTION file (https://travis-ci.org/bnosac/image/jobs/488569507) that's because they are all in subfolders of the main repo.
How do I set it up such that I can do the R CMD check on the different subfolders using this tic framework.
thanks!

@jwijffels
Copy link
Author

jwijffels commented Feb 5, 2019

Ok, finally got this to work after a day of debugging. Things that were not clear:

  • I had to set manually GITHUB_PAT in appveyor / travis / github
  • Same for id_rsa
  • I had to create id_rsa myself using openssl as travis::use_tic() did not do this
  • the package does not work if there is no DESCRIPTION file in the root folder
  • not does it handle R packages with subfolders, so I had to split out the step_add_to_drat in different steps manually
  • I needed to push to the branch gh-pages instead of to the master, giving issues
    In case anyone bumps into this thread: package is here where the CI flows are set up https://github.com/bnosac/image and the drat is here https://github.com/bnosac/drat

I like the idea of this setup although it had some rough edges for my case.
Either way, thank you for the work on this repository!!

@krlmlr
Copy link
Collaborator

krlmlr commented Apr 26, 2019

Thanks for providing this guidance.

Currently, so many tools assume that each repo contains only one package/projects/..., that it's easier for this project to impose this limitation.

@jwijffels
Copy link
Author

Sure, no problem. You are the maintainer, you make the shots.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants