r-hub / devops-issues Goto Github PK

• builders up
• builders disk space
• dokku apps
• crandeps
• test jobs
• crandb updating
• cranatgh updating

Mails from r-hub are considered as spam, often, because the r-hub server is not supposed to send emails, according to the MX records.

Possible solutions:

1. Ask Linux Consortium IT to relay mail from r-hub. Ask them already, waiting for answer.
2. Ask Linux Consortium IT to add MX records for mailgun. Done, waiting for anser.
3. Send mail via mailgun's HTTP API. This requires some rewrite in the front end app, unfortunately.

• monitor
• r-hub.io
• jenkins
• www
• docs

Anything else?

Need a new API parameter for this, and need to update all backend scripts as well.

• frontend web site
• frontend API
• backend (Jenkins job parameter)
• Fix email (takes package name & version from file name currently)
• Linux check script
• Windows check script
• macOS check script
• Solaris check script

r-builder:

• Remove link to r-builder from the web site
• Add deprecation notice to the r-builder repo
• Archive r-builder repo

feedback:

• Move the issues from feedback to rhub
• Add deprication notice to the feedback repo, link to rhub
• Archive feedback repo

This is quite easy, and would solve a lot of issues.

These are the steps needed:

• fix the Jenkins API client's HTTP library to allow multipart POST requests
• fix the Jenkins API client to allow submitting file parameters
• update rhub-frontend to allow specifying the scripts in advanced mode
• check if the rhub-frontend api puts the scripts in the message queue
• update the rhub-backend templates to include the file parameters
• update the rhub-backend Jenkins job creation code to pass the file parameters
• update rhub-backend linux script to pick up the JSON and run it
• update macoscheck to do the same
• update wincheck to do the same
• update solarischeck to do the same
• make sure the log output is reasonable
• update the rhub R package to be able to supply them to the check

https://github.com/bionode/github-project-public seems to be just the tool we need, but I have some issues with it:
bionode/github-project-public#6

• builder-test.r-hub.io
• builder.r-hub.io
• sysreqs.r-hub.io
• install-github.me
• artifacts.r-hub.io
• cran.r-hub.io
• cranbinaries.r-hub.io
• files.r-hub.io
• crandb.r-pkg.org
• r-pkg.org (internal)
• www (intenal)
• cranlogs (internal)
• crandeps (internal)
• rversions (internal)
• crandeps-test (internal)

Questions, suggestions, bug reports, ... : Please file an issue ticket at
GitHub at https://github.com/r-hub/rhub/issues

• without GH app credentials
• without Jenkins
• without Redis
• without logdb
• without mailgun

• Linux
• Windows
• macOS
• Solaris

Because they can hold up the check.

• Linux (nothing to do!)
• Windows
• Solaris
• macOS

• macos
• windows
• solaris

So people do not get emails to @hotmail.com and @outlook.com addresses.

As we are not sending spam, it must be a mistake, or caused another mailgun tenant on the same ip address.

We reported this to both MS and Mailgun.

https://blog.github.com/changelog/2018-08-07-domain-verification/

• windows
• macos
• solaris
• Linux

Because they fill up the disk....

Now that the about page of the builder says to write issues in the R package repo, it can mean that if I say see an issue that belongs to another repo, I could miss a duplicate issue in the R package repo. It nearly happened a minute ago hence my wondering.

I know you @gaborcsardi already sort issues across repos by using a GitHub project, so it might be too much to also create a dashboard like the tidyversedashboard (well creating it shouldn't be too much hassle with Jim's package) to help searching for similar issues before creating one (and to link it from the about page). 🤔