Macos binaries #6421
Macos binaries #6421
Conversation
ben-schwen
requested review from
jangorecki
and removed request for
MichaelChirico
Co-authored-by: Michael Chirico <[email protected]>
|
Nice to see your active contribution in this field. I felt I am the only one that can do glci. Regarding testing. What I used in this case was to add to integration stage extra branch name of THIS branch, next to the master. So then integration also kicks in for this branch. Alternatively, if this branch is up to date with master you could probably try to add this branch name also to deploy stage, but then please don't leave it for a night or so, but confirm after the pipeline finishes, and shorty after finishing testing rerun pipeline for master. It is easy from web ui to run pipeline on demand, without need for any new commits. Ultimately what you can do for testing is to self host gitlab, this is what I did in the distant past, using docker was pretty easy. Although not sure if public runners will work on self hosted instance. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6421 +/- ##
=======================================
Coverage 98.60% 98.60%
=======================================
Files 79 79
Lines 14516 14516
=======================================
Hits 14314 14314
Misses 202 202 ☔ View full report in Codecov by Sentry. |
|
CI results look good. |
|
No binaries for Mac R-devel? |
There is no .pkg for Mac for R-devel and I'm not familiar enough with osx for building it myself |
|
Fair enough. Therefore that most likely implies much less users of r-devel on Mac. |
Follows #6398 and adds binaries for
macosx@jangorecki Is there also a way to pre-test the publishing mechanism without master?
Building + testing on different R versions on
arm64worked fine on CI