Continuous integration (CI)

[fweber144]

(This is basically just a repetition of this comment to put this on the issue tracker.)

I think the reason for Travis CI currently not running automatically is the switch from travis-ci.org to travis-ci.com, as explained in the notification shown on projpred's travis-ci.org site:

Since June 15th, 2021, the building on travis-ci.org is ceased. Please use travis-ci.com from now on.

Since Travis has undergone some changes recently (see, e.g., this blog entry), switching to GitHub Actions might also be an alternative.

[AlejandroCatalina]

To enable this we need admin access, I guess @ Best, Alex

…

________________________________ From: Frank Weber ***@***.***> Sent: Tuesday, October 12, 2021 12:30:41 PM To: stan-dev/projpred ***@***.***> Cc: Subscribed ***@***.***> Subject: [stan-dev/projpred] Continuous integration (CI) (#236) (This is basically just a repetition of this comment<#170 (comment)> to put this on the issue tracker.) I think the reason for Travis CI currently not running automatically is the switch from travis-ci.org to travis-ci.com, as explained in the notification shown on projpred's travis-ci.org site<https://travis-ci.org/github/stan-dev/projpred>: Since June 15th, 2021, the building on travis-ci.org is ceased. Please use travis-ci.com from now on. Since Travis has undergone some changes recently (see, e.g., this blog entry<https://deanattali.com/blog/migrating-travis-to-github/#travis>), switching to GitHub Actions might also be an alternative. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#236>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABZ5FH3SFR4W34HHRIQKS2TUGP54DANCNFSM5F2DKS7A>.

[fweber144]

For GitHub Actions? It depends on whether the default settings for GitHub Actions have been changed. The default should be "Allow all actions" so that by a simple call to usethis::use_github_action_check_standard() (see the blog entry linked above as well as the docs), then following the instructions in its output, and then finally (if desired) modifying .github/workflows/R-CMD-check.yaml, it could be set up without admin access.

In contrast, for removing Travis (which makes sense if switching to GitHub Actions, see also the blog entry linked above), admin access is probably needed, yes.

[fweber144]

However, I don't know if this repo makes use of Travis apart from running checks. In that case, those additional Travis actions would also have to be moved to GitHub Actions (if the checks are moved to GitHub Actions).

EDIT: I forgot that for calculating coverage, this repo probably uses Travis, too. This would be such an additional Travis action which would also have to be moved to GitHub Actions (if the checks are moved to GitHub Actions).

[AlejandroCatalina]

I meant for Travis. I haven’t looked into GitHub actions but it should also work. Best, Alex

…

________________________________ From: Frank Weber ***@***.***> Sent: Tuesday, October 12, 2021 1:46:55 PM To: stan-dev/projpred ***@***.***> Cc: Alejandro Catalina ***@***.***>; Comment ***@***.***> Subject: Re: [stan-dev/projpred] Continuous integration (CI) (#236) However, I don't know if this repo makes use of Travis apart from running checks. In that case, those additional Travis actions would also have to be moved to GitHub Actions (if the checks are moved to GitHub Actions). — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#236 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABZ5FH3DWAM7EY4RIQFE42LUGQGZ7ANCNFSM5F2DKS7A>.