[MINOR][R][BUILD] More reliable detection of R version for Windows in AppVeyor #18859
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR proposes to use https://rversions.r-pkg.org/r-release-win instead of https://rversions.r-pkg.org/r-release to check R's version for Windows correctly.
We met a syncing problem with Windows release (see #15709) before. To cut this short, it was ...
https://rversions.r-pkg.org/r-releasereturns the latest as 3.3.2 and the download link for 3.3.1 becomeswindows/base/oldby our scriptwindows/base/oldbutwindows/baseas the latestwindows/base/oldlink and builds were brokenI believe this problem is not only what we met. Please see krlmlr/r-appveyor@01ce943 and also this
r-release-winAPI came out between 3.3.1 and 3.3.2 (assuming to deal with this issue), please seehttps://github.com/metacran/rversions.app/issues/2.Using this API will prevent the problem although it looks quite rare assuming from the commit logs in https://github.com/metacran/rversions.app/commits/master. After 3.3.2, both
r-release-winandr-releaseare being updated together.How was this patch tested?
AppVeyor tests.