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

update submission to CRAN doc: to rhub 2 #1

Open
plecharpent opened this issue Apr 11, 2024 · 5 comments
Open

update submission to CRAN doc: to rhub 2 #1

plecharpent opened this issue Apr 11, 2024 · 5 comments

Comments

@plecharpent
Copy link
Contributor

plecharpent commented Apr 11, 2024

  • installation

pak::pkg_install("r-hub/rhub")
or

remotes::install_github("r-hub/rhub")

@plecharpent
Copy link
Contributor Author

rhub_setup()
Setting up R-hub v2.
✔ Found R package at /home/plecharpent/Work/projet_stics/projet_SticsRPacks/projet_package_SticsRFiles/SticsRFiles_repos.
✔ Found git repository at /home/plecharpent/Work/projet_stics/projet_SticsRPacks/projet_package_SticsRFiles/SticsRFiles_repos.
✔ Workflow file
/home/plecharpent/Work/projet_stics/projet_SticsRPacks/projet_package_SticsRFiles/SticsRFiles_repos/.github/workflows/rhub.yaml
already exists and it is current.

Notes:
• The workflow file must be added to the default branch of the GitHub repository.
• GitHub actions must be enabled for the repository. They are disabled for forked repositories by default.

Next steps:
• Add the workflow file to git using git add <filename>.
• Commit it to git using git commit (if not committed already).
• Push the commit to GitHub using git push (if not pushed already).
• Call rhub::rhub_doctor() to check that you have set up R-hub correctly.
• Call rhub::rhub_check() to check your package.

@plecharpent
Copy link
Contributor Author

the workflow file must be on the main branch

rhub::rhub_doctor()
✔ Found R package at /home/plecharpent/Work/projet_stics/projet_SticsRPacks/projet_package_SticsRFiles/SticsRFiles_repos.
✔ Found git repository at /home/plecharpent/Work/projet_stics/projet_SticsRPacks/projet_package_SticsRFiles/SticsRFiles_repos.
✔ Found GitHub PAT.
✔ Found repository on GitHub at
https://github.com/SticsRPacks/SticsRFiles.git.
✔ GitHub PAT has the right scopes.
✖ Does the default branch of your git repo have the R-hub workflow file?
Error:
! Could not find R-hub's workflow file in the repository at
https://github.com/SticsRPacks/SticsRFiles.git.
ℹ The workflow file must be at .github/workflows/rhub.yaml.
ℹ If you have added and committed the workflow file, you need to push the
commit to GitHub with git push.
Type .Last.error to see the more details.

@plecharpent
Copy link
Contributor Author

rhub::rhub_doctor()
✔ Found R package at /home/plecharpent/Work/projet_stics/projet_SticsRPacks/projet_package_SticsRFiles/SticsRFiles_repos.
✔ Found git repository at /home/plecharpent/Work/projet_stics/projet_SticsRPacks/projet_package_SticsRFiles/SticsRFiles_repos.
✔ Found GitHub PAT.
✔ Found repository on GitHub at https://github.com/SticsRPacks/SticsRFiles.git.
✔ GitHub PAT has the right scopes.
✔ Found R-hub workflow in default branch, and it is active.
→ WOOT! You are ready to run rhub::rhub_check() on this package.

@plecharpent
Copy link
Contributor Author

rhub::rhub_check()
✔ Found git repository at /home/plecharpent/Work/projet_stics/projet_SticsRPacks/projet_package_SticsRFiles/SticsRFiles_repos.
✔ Found GitHub PAT.

Available platforms (see rhub::rhub_platforms() for details):

1 [VM] linux R-* (any version) ubuntu-latest on GitHub
2 [VM] macos R-* (any version) macos-latest on GitHub
3 [VM] macos-arm64 R-* (any version) macos-14 on GitHub
4 [VM] windows R-* (any version) windows-latest on GitHub
5 [CT] atlas R-devel (2024-04-09 r86391) Fedora Linux 38 (Container Image)
6 [CT] clang-asan R-devel (2024-04-09 r86391) Ubuntu 22.04.4 LTS
7 [CT] clang16 R-devel (2024-04-08 r86370) Ubuntu 22.04.4 LTS
8 [CT] clang17 R-devel (2024-04-08 r86370) Ubuntu 22.04.4 LTS
9 [CT] clang18 R-devel (2024-04-08 r86370) Ubuntu 22.04.4 LTS
10 [CT] donttest R-devel (2024-04-08 r86370) Ubuntu 22.04.4 LTS
11 [CT] gcc13 R-devel (2024-04-09 r86391) Fedora Linux 38 (Container Image)
12 [CT] intel R-devel (2024-04-09 r86391) Fedora Linux 38 (Container Image)
13 [CT] mkl R-devel (2024-04-09 r86391) Fedora Linux 38 (Container Image)
14 [CT] nold R-devel (2024-04-09 r86391) Ubuntu 22.04.4 LTS
15 [CT] nosuggests R-devel (2024-04-09 r86391) Fedora Linux 38 (Container Image)
16 [CT] ubuntu-clang R-devel (2024-04-09 r86391) Ubuntu 22.04.4 LTS
17 [CT] ubuntu-gcc12 R-devel (2024-04-09 r86391) Ubuntu 22.04.4 LTS
18 [CT] ubuntu-next R-4.4.0 beta (2024-04-09 r86391) Ubuntu 22.04.4 LTS
19 [CT] ubuntu-release R-4.3.3 (2024-02-29) Ubuntu 22.04.4 LTS
20 [CT] valgrind R-devel (2024-04-09 r86391) Fedora Linux 38 (Container Image)

Selection (comma separated numbers, 0 to cancel): 4,19,11

✔ Check started: windows, ubuntu-release, gcc13 (knitted-pinkriverdolphin).
See https://github.com/SticsRPacks/SticsRFiles/actions for live output!

@plecharpent
Copy link
Contributor Author

The R Consortium runners
If you don’t want to put your package on GitHub, you can still use the rhub package to run package checks on any supported platform using a shared pool of runners in the https://github.com/r-hub2 GitHub organization.

The process is similar to the first version of R-hub:

  • Set your working directory to the R package you want to check.
  • Obtain a token from R-hub, to verify your email address:

rc_new_token()
(You do not need to do this, if you already submitted packages to a previous version of R-hub from the same machine, using the same email address. Call rc_list_local_tokens() to check if you already have tokens.)

  • Submit a build with

rc_submit()
Select the platforms you want to use, and follow the instructions and the link provided to see your check results.

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

No branches or pull requests

1 participant